Skip to content
Fencer Intel
critical 9.8

CVE-2026-63030 kev in the critical feed json

WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code Execution

published 3mo ago modified 5d ago also BIT-wordpress-2026-63030 , BIT-wordpress-multisite-2026-63030 , EUVD-2026-45280 , GHSA-ff9f-jf42-662q

cvss
9.8
version 3.1, CNA
cisa kev
Exploited
added 2026-07-21
epss
10.6%
EPSS 10.6% chance of exploitation in 30 days, percentile 95%
public exploits
2
Metasploit

Summary

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.

Patch / fix

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.

  • bitnami wordpress 6.9.5, 7.0.2
  • bitnami wordpress-multisite 6.9.5, 7.0.2
  • WordPress WordPress 6.9.5, 7.0.2
  • wordpress Debian 14 7.0.2+dfsg1-1

debian advisories DEBIAN-CVE-2026-63030

Is CVE-2026-63030 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit auxiliary/scanner/http/wordpress_wp2shell_sqli)
  2. Published
  3. Added to CISA KEV
  4. CISA SSVC: exploitation active
  5. CISA patch deadline

Known exploited

Added
3mo ago
Patch by
2026-07-24 (3mo ago)
Ransomware
Not known
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.
Vendor, product
WordPress, Core
CISA name
WordPress Core Interpretation Conflict Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
3mo ago

Exploit prediction

10.65% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami wordpress
>=6.9.0, <6.9.5
>=7.0.0, <7.0.2
6.9.5
7.0.2
bitnami wordpress-multisite
>=6.9.0, <6.9.5
>=7.0.0, <7.0.2
6.9.5
7.0.2

Affected products

  • WordPress WordPress

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of WordPress/wordpress-develop published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.