Quick answers
- Is CVE-2026-24352 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-24352 being exploited in the wild.
- How severe is CVE-2026-24352?
- Critical severity, with a CVSS score of 9.8, published 27 February 2026.
- Which products and versions are affected?
- PluXml CMS 5.8.21, 5.9.0-rc7 (other versions may be affected).
- Is there a fix for CVE-2026-24352?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-24352 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-24352?
- Check whether you run PluXml CMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A session fixation vulnerability (CWE-384) exists in PluXml CMS due to the application's failure to renew the session identifier upon successful user authentication. An attacker can supply a specific session ID to a victim's browser (e.g., via URL parameters or other injection methods); if the victim subsequently authenticates using that ID, the attacker can use the known identifier to hijack the established session. The vulnerability is confirmed in versions 5.8.21 and 5.9.0-rc7. The attack is network-reachable and requires no prior privileges, though it typically involves some level of user interaction to 'fix' the session ID in the victim's browser.
Affected products
- PluXml PluXml CMS 5.8.21, 5.9.0-rc7 (other versions may be affected)
Timeline
- 2026-02-27: advisory: NVD publication date