Skip to content
major vulnerability· requires attention

Critical SQL injection in WordPress core (widely deployed CMS) with high CVSS; affects many public sites and can lead to database compromise and account takeover.

Web

CVE-2026-60137

9.1
Critical
KEV · Exploited in wildEPSS 78%Patch availableJul 18, 2026

SQL injection in WP_Query 'author__not_in' allows DB compromise on vulnerable WordPress sites.

common questions

Is CVE-2026-60137 being exploited?

Yes. CVE-2026-60137 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-60137?

CVE-2026-60137 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-60137?

Yes. A fix has been recorded for CVE-2026-60137. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-60137 affect?

CVE-2026-60137 affects WordPress 6.8.x before 6.8.6, WordPress 6.9.x before 6.9.5, WordPress 7.0.x before 7.0.2, Sites using vulnerable WordPress core with untrusted plugin/theme input. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60137?

Upgrade to 6.8.6/6.9.5/7.0.2, audit plugins/themes for input sanitization, and apply WAF rules

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WordPress 6.8.x before 6.8.6WordPress 6.9.x before 6.9.5WordPress 7.0.x before 7.0.2Sites using vulnerable WordPress core with untrusted plugin/theme input
impact

SQL injection via author__not_in when plugins/themes pass unsanitized input, enabling data exfiltration, DB modification and potential account takeover.

action required

Immediate action required

affected versions
WordPress WordPress
  • affected>= 6.8.0 and < 6.8.6
  • affected>= 6.9.0 and < 6.9.5
  • affected>= 7.0.0 and < 7.0.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free