WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code Execution
CVE-2026-63030GHSA-ff9f-jf42-662q
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (wordpress 7.0.2, 6.9.5; wordpress-multisite 7.0.2, 6.9.5), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Bitnami wordpress
- Affected
- >= 6.9.0, < 6.9.5>= 7.0.0, < 7.0.2
- Fixed in
- 6.9.5, 7.0.2
Bitnami wordpress-multisite
- Affected
- >= 6.9.0, < 6.9.5>= 7.0.0, < 7.0.2
- Fixed in
- 6.9.5, 7.0.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record BIT-wordpress-2026-63030 lists affected ranges: Bitnami wordpress >=6.9.0 =7.0.0 <7.0.2 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record BIT-wordpress-multisite-2026-63030 lists affected ranges: Bitnami wordpress-multisite >=6.9.0 =7.0.0 <7.0.2 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- CISA Known Exploited Vulnerabilities Catalog
CISA added CVE-2026-63030 to the Known Exploited Vulnerabilities catalog on 2026-07-21.
VerifiedObserved Listed in the CISA KEV JSON feed; separate from customer applicability.
Severity and exploitation
- Exploitation
- Confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
- CVSS
- not scored
- EPSS
- CVE-2026-63030: 10.65% estimated exploitation activity in the next 30 days; percentile 95.84 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · evidence added ·
CISA KEV confirmed exploitation for CVE-2026-63030 (date added 2026-07-21). Customer workflow unchanged.
- Revision 2 · amended ·
Amended from osv record BIT-wordpress-multisite-2026-63030
- Revision 1 · created ·
Published from osv record BIT-wordpress-2026-63030
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-63030 Advisory: WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code Execution IDs: CVE-2026-63030, GHSA-ff9f-jf42-662q Record: https://patchnext.com/advisories/cve-2026-63030 (revision 3, source checked 7 Nov 2026, 06:35 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: confirmed: listed in the CISA Known Exploited Vulnerabilities catalog. Vendor response: Vendor fix available; fixed versions by package: wordpress 7.0.2, 6.9.5; wordpress-multisite 7.0.2, 6.9.5. A vendor fix does not mean a deployment is fixed. ## Affected components - Bitnami wordpress: affected >= 6.9.0, < 6.9.5; >= 7.0.0, < 7.0.2; fixed in 6.9.5, 7.0.2 - Bitnami wordpress-multisite: affected >= 6.9.0, < 6.9.5; >= 7.0.0, < 7.0.2; fixed in 6.9.5, 7.0.2 ## Suggested inspection (read-only) - Bitnami wordpress: check the installed version with your package manager. - Bitnami wordpress-multisite: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on wordpress, wordpress-multisite. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/BIT-wordpress-2026-63030 (OSV record BIT-wordpress-2026-63030 lists affected ranges: Bitnami wordpress >=6.9.0 =7.0.0 <7.0.2 (fixed)) - Verified: https://osv.dev/vulnerability/BIT-wordpress-multisite-2026-63030 (OSV record BIT-wordpress-multisite-2026-63030 lists affected ranges: Bitnami wordpress-multisite >=6.9.0 =7.0.0 <7.0.2 (fixed)) - Verified: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (CISA added CVE-2026-63030 to the Known Exploited Vulnerabilities catalog on 2026-07-21.) Commands are suggestions: review each one before running it.
Loading voting…