PluXml CMS versions 5.8.21 and 5.9.0-rc7 contain three vulnerabilities
PluXml CMS versions 5.8.21 and 5.9.0-rc7 contain three vulnerabilities: stored XSS via SVG upload, stored XSS in static pages, and session fixation enabling account hijacking.
Sourcecert.pl — open the original
What to check
- Applies to
- The 3 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
CERT Polska coordinated disclosure of three vulnerabilities affecting PluXml CMS, a content management system. CVE-2026-24350 is a stored cross-site scripting vulnerability in the file upload functionality that allows authenticated attackers to upload malicious SVG files. When victims interact with the uploaded file, arbitrary JavaScript executes in their browser context. CVE-2026-24351 is another stored XSS flaw in the static pages editing feature, enabling attackers with editing privileges to inject malicious HTML and JavaScript that executes when users visit the compromised page.
CVE-2026-24352 is a session fixation vulnerability where the application assigns session identifiers before authentication and fails to regenerate them post-login. This allows attackers to set a known session ID for victims and subsequently hijack their authenticated sessions. CERT Polska confirmed vulnerabilities in versions 5.8.21 and 5.9.0-rc7 through testing, though the vendor did not provide information on the full range of affected versions. The disclosure was responsibly reported by security researcher Arkadiusz Marta.
Organizations using PluXml CMS should assess their exposure and monitor for vendor patches. The combination of XSS and session fixation vulnerabilities could enable attackers to compromise user accounts and inject persistent malicious content into websites running the affected CMS.
Mentioned in this report
Source reporting: https://cert.pl/en/posts/2026/02/CVE-2026-24350
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,572 reports from 147 sources, 724 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs