CVE-2024-22636: PluXml Blog v5.8.9 was discovered to contain a remote code execution (RCE) vulnerability in the Static Pages f

This month

HIGH 8.8DOWNGRADE

CVE-2024-22636 is a high-severity flaw (CVSS 8.8) affecting pluxml. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

PluXml Blog v5.8.9 was discovered to contain a remote code execution (RCE) vulnerability in the Static Pages feature. This vulnerability is exploited via injecting a crafted payload into the Content field.

Why this priority

High severity
Public exploit reference

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

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.3% (top 31%)
CISA exploited list	No
Published	2024-01-25
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: pluxml

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

Am I affected?

Timeline

2024-01-25 21:15 UTCPublished CVE record published
2026-06-17 07:11 UTCUpdated Record last modified

pluxml pluxml DOWNGRADE

Affected: 5.8.9

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.8.9

1. Check installed version

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

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

apt-cache madison pluxml sudo apt install pluxml=<VERSION_BEFORE_5.8.9> 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.9> 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-2024-22636?

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

Is CVE-2024-22636 being exploited?

CVE-2024-22636 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-2024-22636 affect?

CVE-2024-22636 affects pluxml. Severity is high (CVSS 8.8). PluXml Blog v5.8.9 was discovered to contain a remote code execution (RCE) vulnerability in the Static Pages feature. This vulnerability is exploited via injecting a crafted payload into the Content field.

How urgent is CVE-2024-22636?

Priority 53/100. High severity; Public exploit reference

Related CVEs

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

References

← Back to latest CVEs