# CVE-2026-128028: OpenMage magento-lts before 20.18.2 Stored XSS via Product Custom Option SVG Upload


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-7h5v-m38x-m56w, GHSA-v7mx-rv47-452m

## What is CVE-2026-128028?

CVE-2026-128028 is a low-severity vulnerability in OpenMage magento-lts, published on 13 Nov 2026. 

### Official description

OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a stored cross-site scripting vulnerability in Mage_Catalog_Model_Product_Option_Type_File, which accepts guest SVG, XHTML, or XML uploads through product File custom options with an empty allowed-extension list. Unauthenticated attackers can send the file URL under media/custom_options/ to victims, executing script in the store origin and exposing administrator sessions when the admin panel shares that origin.

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

## Which versions are affected by CVE-2026-128028?


## How do I fix CVE-2026-128028?

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

## Is CVE-2026-128028 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128028 and fix it if it is affected.

What it is: CVE-2026-128028 is a low-severity vulnerability in OpenMage magento-lts, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128028 in the wild and no public exploit code.

Affected product: OpenMage magento-lts. 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-2026-128028/ (Markdown: https://insights.sbomify.com/CVE-2026-128028/index.md)
```

## Sources

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

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