CVE-2026-24352: PluXml CMS allows a user's session identifier to be set before authentication

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2026-24352 is a critical-severity flaw (CVSS 9.8) affecting pluxml. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 con

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-384
Published	2026-02-27
Last modified	2026-06-17

Publisher (CNA): CERT.PL · Vendor: pluxml

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-27 12:16 UTCPublished CVE record published
2026-06-17 10:22 UTCUpdated Record last modified

pluxml pluxml DOWNGRADE

Affected: 5.8.21 · 5.9.0 rc7

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.8.21

1. Check installed version

apt-cache policy pluxml || rpm -q pluxml || pluxml --version

2. No fixed release: DOWNGRADE to a release before 5.8.21 (Debian / Ubuntu)

apt-cache madison pluxml sudo apt install pluxml=<VERSION_BEFORE_5.8.21> sudo apt-mark hold pluxml

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pluxml sudo dnf downgrade pluxml-<VERSION_BEFORE_5.8.21> sudo dnf versionlock add pluxml

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-24352?

pluxml: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-24352 being exploited?

CVE-2026-24352 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-24352 affect?

CVE-2026-24352 affects pluxml. Severity is critical (CVSS 9.8). 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 authen

How urgent is CVE-2026-24352?

Priority 48/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-15438 MEDIUM 4.7 UPGRADE A vulnerability was determined in PluXml up to 5.8.22
CVE-2026-24351 MEDIUM 5.4 DOWNGRADE PluXml CMS is vulnerable to Stored XSS in Static Pages editing functionality
CVE-2026-24350 MEDIUM 5.4 DOWNGRADE PluXml CMS is vulnerable to Stored XSS in file uploading functionality
CVE-2025-70129 MEDIUM 5.3 UPGRADE If the anti spam-captcha functionality in PluXml versions 5.8.22 and earlier is enabled, a captcha challenge i
CVE-2025-70128 MEDIUM 6.1 UPGRADE A Stored Cross-Site Scripting (XSS) vulnerability exists in the PluXml article comments feature for PluXml ver

References

← Back to latest CVEs