IDORSSRFAUTH BYPASSJWT FORGERYRACE CONDITIONXXEBROKEN OBJECT-LEVEL AUTHPRIVILEGE ESCALATIONMASS ASSIGNMENTGRAPHQL INTROSPECTION ABUSEIDORSSRFAUTH BYPASSJWT FORGERYRACE CONDITIONXXEBROKEN OBJECT-LEVEL AUTHPRIVILEGE ESCALATIONMASS ASSIGNMENTGRAPHQL INTROSPECTION ABUSE
Impactr Logoimpactr
FeaturesHow it worksEvidencePricingLearnVulnerability DBCompare
  1. Home
  2. Vulnerability Database
  3. CVE-2026-60137
CVE-2026-60137 CISA KEV — actively exploited

WordPress Core SQL Injection Vulnerability

WordPress — WordPress

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.

CVSS scoreMedium

5.9

EPSS — exploitation probabilityLow

4.0%

Vector breakdown

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Published
Jul 17, 2026
Modified
Jul 22, 2026
Added to KEV
Jul 21, 2026
Federal patch due
Aug 4, 2026

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.

Weakness classification

CWE-89Improper Neutralization of Special Elements used in an SQL Command

Proof-of-concept & exploitation references

8 found

Weaponization

Nuclei template

Not found

Metasploit module

Not found

Public repositories whose name or description references CVE-2026-60137, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.

  • Icex0/wp2shell-poc★ 479

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

    updated Jul 22, 2026

  • 0xsha/wp2shell★ 58

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

    updated Jul 22, 2026

  • dinosn/wp2shell-lab★ 36

    Non-destructive detector + Docker lab for wp2shell (CVE-2026-63030 REST /batch/v1 route confusion + CVE-2026-60137 author__not_in SQLi) in WordPress core 6.9.0-6.9.4 / 7.0.0-7.0.1

    updated Jul 22, 2026

  • ZephrFish/wp2shell-scanner★ 21

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

    updated Jul 22, 2026

  • 47Cid/wp2shell-lab★ 13

    Educational PoC + lab for CVE-2026-63030 + CVE-2026-60137: pre-auth SQLi in WordPress core via REST batch-route confusion

    updated Jul 22, 2026

  • NULL200OK/WP2Shell★ 9

    WP2Shell - CVE-2026-63030 / CVE-2026-60137 This tool exploits a critical SQL injection vulnerability in the WordPress REST API `/wp-json/batch/v1` endpoint, allowing unauthenticated attackers to execute arbitrary SQL queries and achieve Remote Code Execution (RCE) on vulnerable WordPress installations.

    updated Jul 21, 2026

  • codeb0ssx/Ultimate-wp2shell★ 8

    wp2shell — Pre-authentication RCE in WordPress Core (CVE-2026-60137 + CVE-2026-63030). Chains an SQL injection in author__not_in with batch-route confusion for unauthenticated remote code execution on WP 6.9.0–6.9.4 / 7.0.0–7.0.1.

    updated Jul 20, 2026

  • bahartanir/wp2shell-scanner★ 7

    CVE-2026-63030 / CVE-2026-60137 - WordPress pre-auth RCE scanner

    updated Jul 20, 2026

References

  • github.com
  • wordpress.org
  • cisa.gov

Frequently asked questions

What is CVE-2026-60137?

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.

How severe is CVE-2026-60137?

CVE-2026-60137 has a CVSS base score of 5.9 out of 10 (CVSS 3.1).

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

Yes. CVE-2026-60137 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Jul 21, 2026, meaning CISA has confirmed evidence of active exploitation.

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

4.0% - meaning FIRST.org's EPSS model estimates a 4.0% probability this vulnerability will be exploited in the wild within 30 days (89% percentile among all scored CVEs).

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

We found 8 public GitHub repositories referencing CVE-2026-60137, though none matched a known Nuclei template or Metasploit module at last check. Review each one before relying on it - see the proof-of-concept section above.

What type of vulnerability is CVE-2026-60137?

CVE-2026-60137 is classified under CWE-89 (CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')).

Cross-checked against

  • NVD (NIST)
  • MITRE CVE Record
  • CISA KEV
  • FIRST.org EPSS
  • GitHub Advisory Database
  • GitHub public repository search

Impactr finds and proves whether CVE-2026-60137 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.

Join the waitlist
← Vulnerability database
Impactr Logoimpactr

Built by hackers, for the code you ship. Autonomous AI penetration testing for modern web apps and APIs.

© 2026 Impactr

Product

FeaturesCoverageUse casesEvidencePricingWaitlist

Resources

VulnerabilitiesVulnerability databaseGuidesComparisonsGlossaryCWE databaseBy industryBy languageHTTP status codesSecurity headers

Company

ContactTwitterLinkedInGitHub