THREAT WATCH
High DD-WRT DD-WRT: CVE-2021-27137 — DD-WRT Stack-Based Buffer Overflow Vulnerability Medium WordPress Core: CVE-2026-60137 — WordPress Core SQL Injection Vulnerability Critical WordPress Core: CVE-2026-63030 — WordPress Core Interpretation Conflict Vulnerability Critical Langflow Langflow: CVE-2026-0770 — Langflow Inclusion of Functionality from Untrusted Control Sphere Vulnerability Critical Fortinet FortiSandbox: CVE-2026-25089 — Fortinet FortiSandbox OS Command Injection Vulnerability Critical Fortinet FortiSandbox: CVE-2026-39808 — Fortinet FortiSandbox OS Command Injection Vulnerability Critical Oracle E-Business Suite: CVE-2026-46817 — Oracle E-Business Suite Improper Privilege Management Vulnerability High KNX Association KNX Protocol Connection Authorization Option 1: CVE-2023-4346 — KNX Association KNX Protocol Connection Authorization Option 1 Overly Restrictive Account Lockout Mechanism Vulnerability High DD-WRT DD-WRT: CVE-2021-27137 — DD-WRT Stack-Based Buffer Overflow Vulnerability Medium WordPress Core: CVE-2026-60137 — WordPress Core SQL Injection Vulnerability Critical WordPress Core: CVE-2026-63030 — WordPress Core Interpretation Conflict Vulnerability Critical Langflow Langflow: CVE-2026-0770 — Langflow Inclusion of Functionality from Untrusted Control Sphere Vulnerability Critical Fortinet FortiSandbox: CVE-2026-25089 — Fortinet FortiSandbox OS Command Injection Vulnerability Critical Fortinet FortiSandbox: CVE-2026-39808 — Fortinet FortiSandbox OS Command Injection Vulnerability Critical Oracle E-Business Suite: CVE-2026-46817 — Oracle E-Business Suite Improper Privilege Management Vulnerability High KNX Association KNX Protocol Connection Authorization Option 1: CVE-2023-4346 — KNX Association KNX Protocol Connection Authorization Option 1 Overly Restrictive Account Lockout Mechanism Vulnerability

CVE-2026-60137 — WordPress Core SQL Injection Vulnerability

Back to Threat Intel Dashboard
Medium CVSS 5.9 Actively exploited · CISA KEV

WordPress Core

CVE-2026-60137 Added Jul 21, 2026 Remediation due in 12 days
TL;DR

WordPress Core is affected by a medium-severity vulnerability (CVE-2026-60137) that is confirmed to be actively exploited in the wild. 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.

What is this vulnerability?

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 it works

This is classified as SQL Injection. In plain terms, an attacker could use this flaw in Core to gain access, disrupt service, or steal data — the exact impact depends on how it’s deployed in your environment.

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

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.

Mitigations

  • Apply the vendor’s security patch or update as soon as it’s available and tested.
  • If no patch exists yet, apply the vendor’s temporary workaround.
  • Limit network exposure of the affected system until it’s patched.
  • Review logs for signs of prior exploitation, especially if it’s flagged for ransomware use.

Recommendations

  • Confirm whether WordPress Core is used anywhere in your environment.
  • Patch internet-facing systems first, then internal ones.
  • Set a reminder ahead of the remediation deadline so it doesn’t slip.
  • Subscribe to the vendor’s security advisories for earlier warning next time.

Compiled from public threat intelligence (CISA Known Exploited Vulnerabilities catalog and the National Vulnerability Database, referenced in 2 public advisories).