CVSS base score: 7.5 (High) CISA · v3.1 · 9.8 (Critical) vendor CNA · v3.1
Two scores are shown because both the vendor's CVE Numbering Authority (CNA) and CISA's Vulnrichment program scored this vulnerability independently — a gap between them reflects differing judgments, not an error.
WordPress Core Interpretation Conflict Vulnerability
Vendor: WordPress Product: Core
WordPress Core contains an interpretation conflict vulnerability that could allow an attacker to perform SQL Injection and achieve Remote Code Execution. This vulnerability can be chained with CVE-2026-60137.
Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 22 points from 2026-07-18, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 98.4% on 2026-08-01.
Check whether a specific version is affected →
What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.
| Date | Source | Article |
|---|---|---|
| 2026-07-21 | BleepingComputer | Critical wp2shell WordPress flaws exploited to install webshells |
| 2026-07-21 | The Hacker News | WordPress wp2shell Exploitation Grows as Public Exploit Fuels Mass Scanning |
| 2026-07-20 | SANS Internet Storm Center | WordPress Exploitation Underway (CVE-2026-63030), (Mon, Jul 20th) |
| 2026-07-20 | Check Point Research | 20th July – Threat Intelligence Report |
Articles from monitored vendor research blogs and security news feeds that specifically mention this CVE. Coverage begins when feed monitoring started; earlier articles are not indexed.
Coverage across public collections only: Nuclei and OpenVAS NVT (scan);
Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM);
Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence
here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by
PoC-in-GitHub (CC0) and are not vetted:
some are fakes and some are malware. Treat them as evidence that code was
published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available
under the Open Database License (ODbL) v1.0;
its individual Vulnerability Tests are licensed
GNU GPL v2.
Where the distribution has shipped a fix, and in which version. Green means the release has resolved it, amber that it is still open. Data from the Debian Security Tracker, used under Debian's MIT / GPLv2+ terms. Debian is upstream of several other distributions, so a fix here often precedes theirs.
| Source | Date | Record |
|---|---|---|
| CISA Vulnrichment | 2026-07-17 | source record → |
| CISA KEV | 2026-07-21 | source record → |
| Date | Advisory | Issuer |
|---|---|---|
| 2026-07-21 | CISA Adds Four Known Exploited Vulnerabilities to Catalog | CISA |
| Date | Tool | Evidence quality | Reference |
|---|---|---|---|
| — | Metasploit | Direct — curated exploit code | WordPress Core wp2shell Unauthenticated SQL Injection via REST Batch Route Confusion |
| 2026-07-18 | Nuclei | Direct — curated exploit code | CVE-2026-63030.yaml |
Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.
CVE.org record → NVD entry → CISA KEV catalog → FortiGuard Labs → Rapid7 AttackerKB →