# CVE-2026-24350: Stored XSS in PluXml CMS

> An authenticated attacker can upload malicious SVG files to execute arbitrary scripts in victims' browsers via stored XSS in PluXml CMS.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-rv67-6qhq-rp2p, UBUNTU-CVE-2026-24350

## What is CVE-2026-24350?

CVE-2026-24350 is a medium-severity cross-site scripting vulnerability in PluXml CMS, published on 27 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

PluXml CMS is vulnerable to Stored XSS in file uploading functionality. An authenticated attacker can upload an SVG file containing a malicious payload, which will be executed when a victim clicks the link associated with the uploaded image.
In version 5.9.0-rc7 clicking the link associated with the uploaded image doesn't execute malicious code but directly accessing the file will still execute the embedded payload.

The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only versions 5.8.21 and 5.9.0-rc7 were tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.

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

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

It affects 1 product.


Products: Pluxml Pluxml.

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

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

## Is CVE-2026-24350 being exploited?

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

## Other vulnerabilities in PluXml CMS

- [CVE-2020-18185](https://insights.sbomify.com/CVE-2020-18185/): Code injection in n/a (critical 9.8)
- [CVE-2024-22636](https://insights.sbomify.com/CVE-2024-22636/): Code injection in n/a (high 8.8)
- [CVE-2022-25018](https://insights.sbomify.com/CVE-2022-25018/): Code injection in n/a (high 8.8)
- [CVE-2012-2227](https://insights.sbomify.com/CVE-2012-2227/): Path traversal in n/a (high 7.5)
- [CVE-2007-3432](https://insights.sbomify.com/CVE-2007-3432/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24350 is a medium-severity cross-site scripting vulnerability in PluXml CMS, published on 27 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-24350 in the wild and no public exploit code.

Affected product: PluXml CMS. 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-24350/ (Markdown: https://insights.sbomify.com/CVE-2026-24350/index.md)
```

## Sources

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

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