“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.9% (79th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
A fix is available — apply it.
WordPress is vulnerable to a remote code execution vulnerability via malicious Postscript file upload by an Author level user or higher.
Prerequisites:
* Imagick and Ghostscript in use on the server
* A malicious user with the upload_files capability
This issue affects all versions of WordPress. Version 7.0.4 has been released, containing a fix for the vulnerability, and as a courtesy to users on older branches the fix has been backported to all branches back to 4.7.
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
August 17, 2026
September 3, 2026
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wordpress | 6.1.1+dfsg1-1 ... 7.1.2+dfsg1-1 (30 versions) |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wordpress | 6.8.1+dfsg1-1, 6.8.3+dfsg1-0+deb13u1, 6.8.3+dfsg1-1, 6.8.6+dfsg1-0+deb13u1, 6.8.7+dfsg1-0+deb13u1 |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| wordpress | 6.8.1+dfsg1-1 ... 7.0.3+dfsg1-1 (7 versions) |
| — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Debian:12:wordpress
CWE-434
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-65640
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.