# CVE-2018-18307: Cross-site scripting in n/a

> Stored XSS in AlchemyCMS image field allows attackers to inject scripts, though vendor disputes validity due to required authentication.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2018
- **Updated:** 29 Aug 2025

## What is CVE-2018-18307?

CVE-2018-18307 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Stored XSS vulnerability has been discovered in version 4.1.0 of AlchemyCMS via the /admin/pictures image field. NOTE: the vendor's position is that this is not a valid report: "The researcher used an authorized cookie to perform the request to a password-protected route. Without that session cookie, the request would have been rejected as unauthorized."

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Alchemy-Cms Alchemy Cms.

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

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

## Is CVE-2018-18307 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-23885](https://insights.sbomify.com/CVE-2026-23885/): AlchemyCMS has Authenticated Remote Code Execution (RCE) via eval injection in ResourcesHelper (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18307 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-18307 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-18307/ (Markdown: https://insights.sbomify.com/CVE-2018-18307/index.md)
```

## Sources

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

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