Skip to content
Server Security Center
KEVmedium5.9

CVE-2026-60137: WordPress Core SQL Injection

WordPress Core · listed in the CISA catalog of actively exploited vulnerabilities since 2026-07-21.

CVSS v3.1 (CVE record)
5.9
medium
EPSS (exploit probability, 30 days)
5.3%
higher than 92.8% of all CVEs
Added to CISA KEV
2026-07-21
US federal due date 2026-08-04
Ubuntu priority
high

CVE-2026-60137 explained

CVE-2026-60137 is an SQL injection flaw in WordPress Core. The author__not_in parameter of WP_Query is not properly sanitised, so a plugin or theme that passes untrusted input to it can expose the database. CISA lists it as known exploited, and Ubuntu rates its priority as high.

Impact

A remote, unauthenticated attacker may be able to read sensitive data from the WordPress database. No user interaction is needed. Exploitation requires a plugin or theme that passes untrusted input to the author__not_in parameter, which makes attacks harder. The CVSS vector shows high confidentiality impact and no integrity or availability impact. CISA has added it to its Known Exploited Vulnerabilities catalog.

Who is affected

Upstream, WordPress 6.8.x before 6.8.6, 6.9.x before 6.9.5 and 7.0.x before 7.0.2 are affected. In Debian 13 (trixie), the wordpress source package is fixed in 6.8.6+dfsg1-0+deb13u1. In Debian 14 (forky), the testing distribution, it is fixed in 7.0.2+dfsg1-1. For Ubuntu 26.10, no fixed version of wordpress has been published yet.

Written with AI from the data on this page and checked against it automatically.

Official 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.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • WordPress
    Affected
    • ≥ 6.8.0, < 6.8.6
    • ≥ 6.9.0, < 6.9.5
    • ≥ 7.0.0, < 7.0.2
    Fixed in
    • 6.8.6
    • 6.9.5
    • 7.0.2

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Identify all hosts running the wordpress package or a WordPress installation from other sources.
  2. On Debian 13 (trixie), update wordpress to 6.8.6+dfsg1-0+deb13u1 or later.
  3. On Debian 14 (forky), update wordpress to 7.0.2+dfsg1-1 or later.
  4. For upstream installations, upgrade to WordPress 6.8.6, 6.9.5, 7.0.2 or later, matching your branch.
  5. Review installed plugins and themes for code that passes user input to WP_Query's author__not_in parameter.
  6. Because the flaw is known exploited, review database and web server logs for signs of compromise.

Ubuntu 26.10 has no fixed wordpress package yet. Until one is published, limit network exposure of the site and disable or remove plugins and themes that pass untrusted input to author__not_in. Keep only trusted, maintained extensions installed, and monitor logs for unusual queries. Apply the update as soon as Ubuntu publishes it.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace wordpress with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="wordpress"'

2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="wordpress"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

No fixed version yet on one release

Ubuntu 26.10: no fixed version of wordpress yet, so every installed version there is affected. Until a fix is published:

  • Follow the vendor's advisory for a mitigation or patch: github.com/WordPress/wordpress-develop/security/advisorie…
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-89 SQL Injection

Questions about CVE-2026-60137

Is every WordPress site exploitable?
No. The description says exploitation requires a plugin or theme that passes untrusted input to the author__not_in parameter of WP_Query. Sites without such code are not exposed this way. However, auditing every extension is difficult, so updating is the safer choice.
Why is this urgent if the CVSS severity is medium?
CISA lists the flaw in its Known Exploited Vulnerabilities catalog, which means attacks have been observed. Ubuntu also rates its priority as high. The attack needs no authentication and can expose confidential database contents.
Does Debian 14 (forky) count as a fixed stable release?
No. Debian 14 (forky) is the testing distribution, not a stable release. It does carry the fix in 7.0.2+dfsg1-1. For production systems on a stable release, Debian 13 (trixie) has the fix in 6.8.6+dfsg1-0+deb13u1.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.