How severe is CVE-2026-63030?

No CVSS score has been assigned to CVE-2026-63030 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-63030?

CVE-2026-63030 affects the following packages: wordpress (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2026-63030?

Update wordpress to 6.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-63030 is resolved across your whole dependency graph.

How do I detect CVE-2026-63030 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wordpress, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-63030 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2026-63030 actively exploited in the wild?

Yes. There are 29 known exploit references for CVE-2026-63030, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2026-63030?

CVE-2026-63030 has an EPSS (Exploit Prediction Scoring System) score of 10.6%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2026-63030 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-63030 (WordPress Core Interpretation Conflict Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-07-21. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-07-24. The required action was: 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. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-63030?

CVE-2026-63030 is classified as CWE-436 (CWE-436). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2026-63030?

A Nuclei detection template exists for CVE-2026-63030, meaning automated scanners can fingerprint it. 4 Metasploit modules reference CVE-2026-63030, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-63030 published, and has it been updated?

CVE-2026-63030 was published on July 27, 2026 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

CISA KEV · ACTIVELY EXPLOITED

CVE-2026-63030 — wordpress

CVE-2026-63030 is a CWE-436 vulnerability in wordpress. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-07-21) — treat it as actively exploited and patch now. A fix is available for wordpress — see the affected versions and patch details below.

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

Also known asBIT-wordpress-multisite-2026-63030

Published

Jul 27, 2026

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

29 known

Exploitation data as of Oct 15, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-07-21. Federal agencies were required to remediate by 2026-07-24.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-63030.

EPSS Exploitation Probability

via FIRST.org ↗

10.6%probability of exploitation in next 30 days

Moderate Risk+0.53%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦wordpress

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`wordpress`	≥ 6.9.0&&< 6.9.5	6.9.5

Affected Products

1 product · 2 configurations

Application

wordpresswordpress

≥ 7.0 && < 7.0.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Icex0/wp2shell-poc

wp2shell (CVE-2026-63030 & CVE-2026-60137) - full RCE chain

⭐ 784🍴 176Sep 2026

arvindear/wp2shell-PoC

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

⭐ 565🍴 53Sep 2026

0xsha/wp2shell

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

⭐ 111🍴 32Sep 2026

ZephrFish/wp2shell-scanner

CVE-2026-63030, CVE-2026-60137, wp2shell scanner

⭐ 66🍴 14Sep 2026

dinosn/wp2shell-lab

Non-destructive detector + Docker lab for wp2shell (CVE-2026-63030 REST

⭐ 63🍴 19Sep 2026

NULL200OK/WP2Shell

WP2Shell - CVE-2026-63030 / CVE-2026-60137 This tool exploits a critical

⭐ 16🍴 5Sep 2026

mcipekci/wp2shell

Pre-auth RCE PoC for WordPress core — chains CVE-2026-63030 (REST /batch

⭐ 15🍴 9Jul 2026

securelayer7/WordPresShell

Pre-auth RCE PoC for CVE-2026-63030 / CVE-2026-60137 (WordPress core)

⭐ 15🍴 3Sep 2026

47Cid/wp2shell-lab

Educational PoC + lab for CVE-2026-63030 + CVE-2026-60137: pre-auth SQLi

⭐ 15🍴 2Aug 2026

mhtsec/CVE-2026-63030

WordPress 未授权RCE EXP | CVE-2026-63030

⭐ 14🍴 4Sep 2026

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wordpress, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wordpress to 6.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-63030 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

How to detect CVE-2026-63030

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2026-63030 -u https://target

Template: WordPress Core 6.9-7.0.1 - Pre-Auth Batch-Route Confusion
Severity: critical
Impact: The route confusion allows unauthenticated requests to reach REST API handlers they should not be able to access. When chained with the associated SQL injection, an unauthenticated attacker can read the entire WordPress database (including user credential hashes) and escalate to full site compromise and remote code execution.
Remediation: Update WordPress immediately to version 6.9.5 or 7.0.2. As a temporary mitigation, block POST requests to /wp-json/batch/v1 and /?rest_route=/batch/v1 at the WAF or reverse proxy level.

Template by ProjectDiscovery nuclei-templates (slcyber, mielverkerken, pdteam), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-63030 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works