# CVE-2018-7486: Code injection in n/a

> Remote attackers can execute arbitrary code via path traversal in the [m] tag, requiring file upload capability.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pcgv-6rcf-4897

## What is CVE-2018-7486?

CVE-2018-7486 is a high-severity code injection vulnerability in n/a, published on 26 Feb 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Blue River Mura CMS before v7.0.7029 supports inline function calls with an [m] tag and [/m] end tag, without proper restrictions on file types or pathnames, which allows remote attackers to execute arbitrary code via an [m]$.dspinclude("../pathname/executable.jpeg")[/m] approach, where executable.jpeg contains ColdFusion Markup Language code. This can be exploited in conjunction with a CKFinder feature that allows file upload.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2018-7486?

It affects 1 product.


Products: Blueriver Muracms.

## How do I fix CVE-2018-7486?

No fix has been published for CVE-2018-7486 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-7486 being exploited?

There is no known exploitation of CVE-2018-7486 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-8302](https://insights.sbomify.com/CVE-2017-8302/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7486 and fix it if it is affected.

What it is: CVE-2018-7486 is a high-severity code injection vulnerability in n/a, published on 26 Feb 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7486 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-7486/ (Markdown: https://insights.sbomify.com/CVE-2018-7486/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-7486
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-7486
- OSV: https://osv.dev/vulnerability/CVE-2018-7486

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-7486/
Summaries are generated and may contain mistakes; the official description above is the record.