PatchTheCVEpluxml vulnerabilities and fixes
Recent CVEs affecting pluxml, with upgrade or downgrade steps. 8 tracked.
pluxml has 8 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-03-10. Highest priority: CVE-2024-22636 (score 53/100).
- CVE-2025-15438 MEDIUM 4.7 UPGRADE A vulnerability was determined in PluXml up to 5.8.22
- CVE-2026-24352 CRITICAL 9.8 DOWNGRADE PluXml CMS allows a user's session identifier to be set before authentication
- 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
- CVE-2025-67436 MEDIUM 6.5 DOWNGRADE Authenticated Remote Code Execution (RCE) in PluXml CMS 5.8.22 allows an attacker with administrator panel acc
- CVE-2024-22636 HIGH 8.8 DOWNGRADE PluXml Blog v5.8.9 was discovered to contain a remote code execution (RCE) vulnerability in the Static Pages f
FAQ
How do I fix pluxml vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is pluxml being exploited right now?
None of the tracked pluxml CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which pluxml CVE should I patch first?
CVE-2024-22636 currently ranks highest (53/100): PluXml Blog v5.8.9 was discovered to contain a remote code execution (RCE) vulnerability in the Static Pages f.