Skip to content
Fencer Vulns
medium 5.9

CVE-2026-60137 kev in the critical feed json

WordPress < 7.0.2 - Facilitated SQL Injection via author__not_in in WP_Query

published 2026-07-17 3 mo ago modified 2026-11-07 2 d ago also BIT-wordpress-2026-60137 , BIT-wordpress-multisite-2026-60137 , EUVD-2026-45279 , GHSA-fpp7-x2x2-2mjf

cvss
5.9
version 3.1, CNA
cisa kev
Exploited
added 2026-07-21
epss
5.3%
EPSS 5.3% chance of exploitation in 30 days, percentile 92%
public exploits
2
Metasploit

Summary

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.

Patch / fix

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.

  • bitnami wordpress 6.8.6, 6.9.5, 7.0.2
  • bitnami wordpress-multisite 6.8.6, 6.9.5, 7.0.2
  • WordPress WordPress 6.8.6, 6.9.5, 7.0.2
  • wordpress Debian 13 6.8.6+dfsg1-0+deb13u1
  • wordpress Debian 14 7.0.2+dfsg1-1

debian advisories DEBIAN-CVE-2026-60137

Timeline

  1. First public exploit (Metasploit auxiliary/scanner/http/wordpress_wp2shell_sqli)
  2. Published
  3. Added to CISA KEV
  4. CISA SSVC: exploitation active
  5. CISA patch deadline

Known exploited

Added
3 mo ago
Patch by
2026-08-04 (3 mo ago)
Ransomware
Not known
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.
Vendor, product
WordPress, Core
CISA name
WordPress Core SQL Injection Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
3 mo ago

Exploit prediction

5.32% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami wordpress
>=6.8.0, <6.8.6
>=6.9.0, <6.9.5
>=7.0.0, <7.0.2
6.8.6
6.9.5
7.0.2
bitnami wordpress-multisite
>=6.8.0, <6.8.6
>=6.9.0, <6.9.5
>=7.0.0, <7.0.2
6.8.6
6.9.5
7.0.2

Affected products

  • WordPress WordPress

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of WordPress/wordpress-develop published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.