Is CVE-2026-60137 automatically exploitable on my domain?

Not necessarily. ThreatPort treats CVE-2026-60137 as a risk signal that must be connected to observed external assets, detected technologies, and reachable services.

What does ThreatPort check for CVE-2026-60137?

ThreatPort looks for public asset evidence, service fingerprints, CVE-linked technology signals, exposed endpoints, weak DNS/TLS posture, and remediation context.

Should this replace vendor advisories?

No. Use vendor advisories and official patches for final remediation decisions; use ThreatPort to find externally visible exposure and prove cleanup.

CVE-2026-60137 Core exposure check

From CVE Record to External Exposure

WordPress Core contains a SQL injection vulnerability when a plugin or theme passes untrusted input to the parameter. This vulnerability can be chained with CVE-2026-63030 to allow an unauthenticated attacker to gain remote code execution on default WordPress installations.

WordPress Core SQL Injection Vulnerability should be triaged by matching the affected vendor and product to live, internet-facing assets rather than treating the CVE as an abstract feed item. ThreatPort focuses on the first question that budget-constrained IT leaders and CISOs ask: what can an outside observer find today, how severe is it, and what should be fixed first?

Known Exploitation Record

CISA KEV status: Listed as actively exploited
Added to KEV: 2026-07-21
Federal patch deadline (BOD 22-01): 2026-08-04
Known ransomware campaign use: Not recorded
EPSS exploitation probability: 20.39% (97p)
Weakness type: CWE-89
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.

Source: CISA Known Exploited Vulnerabilities catalog and FIRST.org EPSS.

What ThreatPort Checks

Identify externally reachable services that appear related to WordPress Core.

Map detected technologies to CVE-2026-60137, severity context, and practical remediation priority.

Check TLS, DNS, headers, exposed panels, stale endpoints, and service fingerprints from a public attacker perspective.

Produce a concise scorecard first, then unlock deeper AI pentest evidence and PDF reporting when remediation planning begins.

The output is intentionally practical: ownership clues, risk context, remediation hints, and repeatable evidence that can be shared with technical teams or leadership. It is not positioned as magic compliance automation or a replacement for human security judgment.

Lean security teams rarely need another broad vulnerability list. They need to know whether an exposed endpoint, an expired certificate, a weak DNS setting, or a CVE-linked service is likely to affect the systems they actually run. ThreatPort scans from the outside in, ranks what it finds by real reachability rather than raw CVSS, and hands back evidence a team can act on the same day.

Route-Specific Evidence Profile

CVE-2026-60137 affects WordPress Core, a CWE-89 weakness. This page exists to answer one question: is anything you own externally reachable and running it.

Assets This Page Should Care About

Public domains Subdomains Externally reachable web apps TLS endpoints DNS records

Signals Worth Prioritizing

Forgotten subdomains

Weak DNS or email controls

Outdated services

Risky headers

What Should Be Reviewed First in This Context?

For teams running WordPress Core, the first step is to validate internet-facing assets with business relevance instead of producing a generic vulnerability list.