How severe is CVE-2026-60137?

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

Which packages are affected by CVE-2026-60137?

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

How do I fix CVE-2026-60137?

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

How do I detect CVE-2026-60137 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-60137 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-60137 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2026-60137, 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-60137?

CVE-2026-60137 has an EPSS (Exploit Prediction Scoring System) score of 5.3%, placing it in the 93th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

Yes. CVE-2026-60137 (WordPress Core SQL Injection 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-08-04. 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-60137?

CVE-2026-60137 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

4 Metasploit modules reference CVE-2026-60137, 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-60137 published, and has it been updated?

CVE-2026-60137 was published on July 27, 2026 and was last updated on October 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-60137 — wordpress

CVE-2026-60137 is a SQL Injection 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 - Facilitated SQL Injection via author__not_in in WP_Query

Also known asBIT-wordpress-multisite-2026-60137

Published

Jul 27, 2026

Updated

Oct 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Oct 16, 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-08-04.
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-60137.

EPSS Exploitation Probability

via FIRST.org ↗

5.3%probability of exploitation in next 30 days

Lower Risk-0.58%

Lower risk than most CVEs93th percentile — riskier than 93% 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.8.x before 6.8.6, 6.9.x before 6.9.5, and 7.0.x before 7.0.2 does not properly sanitise the author__not_in parameter of WP_Query, which could allow SQL Injection when a plugin or theme passes untrusted input to the parameter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`wordpress`	≥ 6.8.0&&< 6.8.6	6.8.6

Affected Products

1 product · 3 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.

codeb0ssx/Ultimate-wp2shell

wp2shell — Pre-authentication RCE in WordPress Core (CVE-2026-60137 + CV

⭐ 10🍴 2Aug 2026

Colere-Sys/wp2shell-poc

Analysis and end-to-end implementation of the patched wordpress RCE vuln

⭐ 3🍴 0Aug 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.8.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-60137 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-60137 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works