CVE-2026-63030

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-07-21), indicating real-world exploitation has been confirmed by US federal agencies. It is also listed on ENISA's EU Known Exploited Vulnerabilities catalogue (Source: ENISA EUVD). A secondary CVSS source baseline 9.8 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, ENISA's EU Known Exploited Vulnerabilities catalogue, a secondary CVSS source
Exploited in the wild

Also known asEUVD-2026-45280 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 2 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedENISA EU KEV: Listed (Source: ENISA EUVD)EPSS PROB: 11%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: 2

A fix is available — apply it.

WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoint route confusion issue which, combined with the author__not_in WP_Query SQL Injection (CVE-2026-60137), could allow an attacker to perform SQL Injection and achieve Remote Code Execution.

Internet exposure · derived from Shodan data

2 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2026-63030, in our KEV-Exposure radar’s Shodan-derived sample.

across 2 hosting countries (United Kingdom, United States)top: wordpress
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (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.
Action: A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
11%
EPSS %ILE
95th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
11% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and ENISA EU KEV (Source: ENISA EUVD) and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

ENISA EU KEV: listed September 21, 2026, reported by ENISA.

Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement. How a listing moves the EG score

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (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)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (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

CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://wordpress.org/news/2026/07/wordpress-7-0-2-release/ · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-63030

Published

July 17, 2026

Last Modified

October 8, 2026

Advisory Details (3)

Auto-updated Nov 13, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa, github.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-63030
Web page

WordPress 7.0.2 Release | WordPress News

https://wordpress.org/news/2026/07/wordpress-7-0-2-release/
GitHub advisoryMentions a patch (unverified)

REST API batch-route confusion and SQL injection issue leading to Remote Code Execution · Advisory · WordPress/wordpress-develop · GitHub

https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-ff9f-jf42-662q

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress6.8.1+dfsg1-1, 6.8.3+dfsg1-1, 6.9+dfsg1-1, 6.9.4+dfsg1-1, 7.0+dfsg1-1
  • every version up to 7.0.2+dfsg1-1: fixed in 7.0.2+dfsg1-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 208 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 11% · 95th percentile
  2. 2026-11-12 20:18 UTCEchelonGraph re-scored
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 11% · 95th percentile
  4. 2026-11-11 19:20 UTCEchelonGraph re-scored
  5. 2026-11-11 16:40 UTCEPSS rescoreEPSS 11% · 95th percentile
  6. 2026-11-10 18:23 UTCEchelonGraph re-scored
  7. 2026-11-10 16:45 UTCEPSS rescoreEPSS 11% · 95th percentile
  8. 2026-11-09 17:26 UTCEchelonGraph re-scored
  9. 2026-11-09 16:35 UTCEPSS rescoreEPSS 11% · 95th percentile
  10. 2026-11-08 16:40 UTCEPSS rescoreEPSS 11% · 95th percentile
  11. 2026-11-08 05:05 UTCEchelonGraph re-scored
  12. 2026-11-07 16:39 UTCEPSS rescoreEPSS 11% · 95th percentile
  13. 2026-11-07 04:08 UTCEchelonGraph re-scored
  14. 2026-11-06 16:39 UTCEPSS rescoreEPSS 11% · 95th percentile
  15. 2026-11-06 03:06 UTCEchelonGraph re-scored
  16. 2026-11-05 16:38 UTCEPSS rescoreEPSS 11% · 95th percentile
  17. 2026-11-05 02:09 UTCEchelonGraph re-scored
  18. 2026-11-04 16:36 UTCEPSS rescoreEPSS 11% · 95th percentile
  19. 2026-11-04 01:11 UTCEchelonGraph re-scored
  20. 2026-11-03 16:48 UTCEPSS rescoreEPSS 11% · 95th percentile
  21. 2026-11-03 00:11 UTCEchelonGraph re-scored
  22. 2026-11-01 23:11 UTCEchelonGraph re-scored
  23. 2026-11-01 16:35 UTCEPSS rescoreEPSS 11% · 95th percentile
  24. 2026-10-31 22:14 UTCEchelonGraph re-scored
  25. 2026-10-31 16:33 UTCEPSS rescoreEPSS 11% · 95th percentile
Show 75 more
  1. 2026-10-30 21:13 UTCEchelonGraph re-scored
  2. 2026-10-30 16:34 UTCEPSS rescoreEPSS 11% · 95th percentile
  3. 2026-10-29 20:16 UTCEchelonGraph re-scored
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 11% · 95th percentile
  5. 2026-10-28 19:19 UTCEchelonGraph re-scored
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 11% · 95th percentile
  7. 2026-10-27 18:23 UTCEchelonGraph re-scored
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 11% · 95th percentile
  9. 2026-10-26 17:26 UTCEchelonGraph re-scored
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 11% · 95th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 11% · 95th percentile
  12. 2026-10-25 13:47 UTCEchelonGraph re-scored
  13. 2026-10-25 13:46 UTCENISA EU KEV listingEUVD-2026-45280 · listed September 21, 2026 · reported by ENISA · Source: ENISA EUVD
  14. 2026-10-24 22:14 UTCEchelonGraph re-scored
  15. 2026-10-24 16:33 UTCEPSS rescoreEPSS 11% · 95th percentile
  16. 2026-10-23 21:16 UTCEchelonGraph re-scored
  17. 2026-10-23 16:32 UTCEPSS rescoreEPSS 11% · 95th percentile
  18. 2026-10-22 20:16 UTCEchelonGraph re-scored
  19. 2026-10-22 16:35 UTCEPSS rescoreEPSS 11% · 95th percentile
  20. 2026-10-21 19:16 UTCEchelonGraph re-scored
  21. 2026-10-21 16:33 UTCEPSS rescoreEPSS 11% · 95th percentile
  22. 2026-10-20 18:19 UTCEchelonGraph re-scored
  23. 2026-10-20 16:33 UTCEPSS rescoreEPSS 11% · 95th percentile
  24. 2026-10-19 17:22 UTCEchelonGraph re-scored
  25. 2026-10-19 16:32 UTCEPSS rescoreEPSS 11% · 95th percentile
  26. 2026-10-18 03:23 UTCEchelonGraph re-scored
  27. 2026-10-17 16:35 UTCEPSS rescoreEPSS 11% · 95th percentile
  28. 2026-10-16 18:29 UTCEchelonGraph re-scored
  29. 2026-10-16 16:43 UTCEPSS rescoreEPSS 11% · 95th percentile
  30. 2026-10-15 17:30 UTCEchelonGraph re-scored
  31. 2026-10-15 16:32 UTCEPSS rescoreEPSS 11% · 95th percentile
  32. 2026-10-14 16:33 UTCEPSS rescoreEPSS 11% · 95th percentile
  33. 2026-10-14 08:16 UTCEchelonGraph re-scored
  34. 2026-10-13 16:34 UTCEPSS rescoreEPSS 11% · 95th percentile
  35. 2026-10-13 07:18 UTCEchelonGraph re-scored
  36. 2026-10-12 16:34 UTCEPSS rescoreEPSS 11% · 95th percentile
  37. 2026-10-12 15:49 UTCEchelonGraph re-scored
  38. 2026-10-11 19:19 UTCEchelonGraph re-scored
  39. 2026-10-11 16:48 UTCEchelonGraph re-scored
  40. 2026-10-11 14:10 UTCEchelonGraph re-scored
  41. 2026-10-11 13:49 UTCEPSS rescoreEPSS 11% · 95th percentile
  42. 2026-10-11 12:00 UTCEchelonGraph re-scored
  43. 2026-10-10 21:18 UTCEchelonGraph re-scored
  44. 2026-10-10 20:00 UTCEPSS rescoreEPSS 11% · 95th percentile
  45. 2026-10-09 23:19 UTCEchelonGraph re-scored
  46. 2026-10-09 20:07 UTCEPSS rescoreEPSS 11% · 95th percentile
  47. 2026-10-08 18:03 UTCEchelonGraph re-scored
  48. 2026-10-08 17:13 UTCEPSS rescoreEPSS 11% · 95th percentile
  49. 2026-10-08 02:37 UTCEchelonGraph re-scored
  50. 2026-10-07 23:48 UTCEPSS rescoreEPSS 10% · 95th percentile
  51. 2026-10-07 19:19 UTCEchelonGraph re-scored
  52. 2026-10-07 18:47 UTCEchelonGraph re-scored▲ 0.80
  53. 2026-10-07 18:46 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  54. 2026-10-06 18:56 UTCEchelonGraph re-scored
  55. 2026-10-06 15:18 UTCEPSS rescoreEPSS 10% · 95th percentile
  56. 2026-10-05 20:59 UTCEchelonGraph re-scored
  57. 2026-10-05 17:43 UTCEPSS rescoreEPSS 10% · 95th percentile
  58. 2026-10-05 02:42 UTCEchelonGraph re-scored
  59. 2026-10-04 23:22 UTCEPSS rescoreEPSS 10% · 95th percentile
  60. 2026-10-03 17:47 UTCEchelonGraph re-scored
  61. 2026-10-03 14:26 UTCEPSS rescoreEPSS 10% · 95th percentile
  62. 2026-10-02 19:53 UTCEchelonGraph re-scored
  63. 2026-10-02 17:56 UTCEPSS rescoreEPSS 10% · 95th percentile
  64. 2026-10-01 21:54 UTCEchelonGraph re-scored
  65. 2026-10-01 19:50 UTCEPSS rescoreEPSS 10% · 95th percentile
  66. 2026-09-30 16:37 UTCEchelonGraph re-scored
  67. 2026-09-30 15:03 UTCEPSS rescoreEPSS 10% · 95th percentile
  68. 2026-09-29 18:35 UTCEchelonGraph re-scored
  69. 2026-09-29 00:18 UTCEchelonGraph re-scored
  70. 2026-09-28 16:59 UTCEchelonGraph re-scored
  71. 2026-09-28 13:51 UTCEPSS rescoreEPSS 10% · 95th percentile
  72. 2026-09-27 21:51 UTCCISA KEV update
  73. 2026-09-27 15:23 UTCEchelonGraph re-scored
  74. 2026-09-26 17:26 UTCEchelonGraph re-scored
  75. 2026-09-26 15:59 UTCEPSS rescoreEPSS 10% · 95th percentile

Publicly available exploits

(20 references, 10 shown)

Public exploit code is referenced for this CVE (2 Metasploit modules, 15 GitHub PoCs), as are 1 Nuclei detection template, 2 GitHub checker repositories. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitauxiliary/scanner/http/wordpress_wp2shell_sqli✓ verified
    Published Aug 25, 2026

    WordPress Core wp2shell Unauthenticated SQL Injection via REST Batch Route Confusion

    Open source ↗
  • Metasploitexploit/multi/http/wp_batch_desync_rce✓ verified
    Published Aug 7, 2026

    WordPress WP2Shell REST API Batch Route Confusion SQLi to RCE

    Open source ↗
  • GitHub PoCsowarma/wp2shell-PoC
    Published Aug 5, 2026

    CVE-2026-63030 & CVE-2026-60137 RCE chain proof-of-concept

    Open source ↗
  • GitHub PoCmcipekci/wp2shell
    Published Jul 22, 2026

    Pre-auth RCE PoC for WordPress core — chains CVE-2026-63030 (REST /batch/v1 route-confusion desync) with CVE-2026-60137 (author__not_in SQLi) into an unauthenticated shell. Authorized testing only.

    Open source ↗
  • GitHub PoCbahartanir/wp2shell-scanner
    Published Jul 19, 2026

    CVE-2026-63030 / CVE-2026-60137 - WordPress pre-auth RCE scanner

    Open source ↗
  • GitHub PoCikow/wp2shell
    Published Jul 19, 2026

    wp2shell — WordPress Core Pre-Auth RCE (CVE-2026-63030 + CVE-2026-60137). Exploit toolkit + remediation.

    Open source ↗
  • GitHub checkerdinosn/wp2shell-lab
    Published Jul 18, 2026

    Non-destructive detector + Docker lab for wp2shell (CVE-2026-63030 REST /batch/v1 route confusion + CVE-2026-60137 author__not_in SQLi) in WordPress core 6.9.0-6.9.4 / 7.0.0-7.0.1

    Open source ↗
  • GitHub PoC0xsha/wp2shell
    Published Jul 18, 2026

    CVE-2026-63030 + CVE-2026-60137 - “wp2shell”: unauthenticated RCE in WordPress core

    Open source ↗
  • GitHub PoC47Cid/wp2shell-lab
    Published Jul 18, 2026

    Educational PoC + lab for CVE-2026-63030 + CVE-2026-60137: pre-auth SQLi in WordPress core via REST batch-route confusion

    Open source ↗
  • GitHub PoC4minx/CVE-2026-63030
    Published Jul 18, 2026

    CVE-2026-63030 (wp2shell) POC.

    Open source ↗

Frequently asked(6)

What is CVE-2026-63030?
CVE-2026-63030 is a critical-severity vulnerability; its CVE record was published on July 17, 2026. WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoint route confusion issue which, combined with the author__not_in WP_Query SQL Injection (CVE-2026-60137), could allow an attacker to perform SQL Injection and achieve Remote Code Execution.
When was the CVE record for CVE-2026-63030 published?
The CVE record for CVE-2026-63030 was published on July 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-63030 actively exploited?
Yes. CISA added CVE-2026-63030 to the Known Exploited Vulnerabilities catalog on July 21, 2026, affecting WordPress Core. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it. ENISA's EU Known Exploited Vulnerabilities catalogue lists CVE-2026-63030 (added September 21, 2026, reported by ENISA): ENISA records its exploitation in the wild. Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement.
What is the CVSS score of CVE-2026-63030?
CVE-2026-63030 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
Which products are affected by CVE-2026-63030?
CVE-2026-63030 affects WordPress Core. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2026-63030?
A fix for CVE-2026-63030 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63030

Explore →

Is Your Infrastructure Affected by CVE-2026-63030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.