CVE-2022-25018: Pluxml v5.8.7 was discovered to allow attackers to execute arbitrary code via crafted PHP code inserted into s

This month

HIGH 8.8DOWNGRADE

CVE-2022-25018 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 v5.8.7 was discovered to allow attackers to execute arbitrary code via crafted PHP code inserted into static pages.

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	2.7% (top 14%)
CISA exploited list	No
Weakness	CWE-94
Published	2022-03-01
Last modified	2026-07-09

Publisher (CNA): MITRE · Vendor: pluxml

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

Am I affected?

Timeline

2022-03-01 02:15 UTCPublished CVE record published
2026-07-09 01:17 UTCUpdated Record last modified

pluxml pluxml DOWNGRADE

Affected: 5.8.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.8.7

1. Check installed version

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

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

apt-cache madison pluxml sudo apt install pluxml=<VERSION_BEFORE_5.8.7> 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.7> 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-2022-25018?

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

Is CVE-2022-25018 being exploited?

CVE-2022-25018 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-2022-25018 affect?

CVE-2022-25018 affects pluxml. Severity is high (CVSS 8.8). Pluxml v5.8.7 was discovered to allow attackers to execute arbitrary code via crafted PHP code inserted into static pages.

How urgent is CVE-2022-25018?

Priority 57/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2025-15438 MEDIUM 4.7 UPGRADE A vulnerability was determined in PluXml up to 5.8.22
CVE-2022-25020 MEDIUM 5.4 DOWNGRADE A cross-site scripting (XSS) vulnerability in Pluxml v5.8.7 allows attackers to execute arbitrary web scripts
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

References

← Back to latest CVEs