SAK T.E.CTechnology · Evaluation · Compliance Free domain checkCheck

Exploited vulnerabilities / CVE-2026-119977

Confirmed exploited · exploited vulnerability · WordPress Core

CVE-2026-119977

WordPress Core exploited vulnerability, confirmed exploited in the wild.

WordPress WordPress Core contains a time-of-check time-of-use (TOCTOU) race condition vulnerability that could allow unauthenticated attackers to execute code on the server during the upgrade window. This is due to predictable, web-accessible staging paths used during full-package core upgrades.

1.2%chance of exploitation in the next 30 days (EPSS), 68th percentile
3 Novadded to CISA's Known Exploited Vulnerabilities list, 2026
6 Novfederal remediation deadline, already passed
Passedpast the deadline: patch now
CISA's name for itWordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability
Vendor and productWordPress · WordPress Core
Typeexploited vulnerability · CWE-367
ExploitedConfirmed by CISA listed 3 November 2026
Likelihoodscored lower by EPSS, but already confirmed exploited, which outranks any prediction
Deadline6 November 2026 · already passed
Used in ransomwareNot reported
Advisorieswordpress.org ↗ · www.wordfence.com ↗ · www.cisa.gov ↗ · www.cisa.gov ↗
What to do

Three steps, in this order

Step 1

Apply the vendor's fix or mitigation; CISA lists only vulnerabilities seen exploited.

Step 2

If you cannot patch now, restrict network access to the affected product.

Step 3

Check for signs of compromise since the date it was added to the list.

CISA's required actionApply 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.
Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Questions

CVE-2026-119977 in short

Is CVE-2026-119977 being exploited?

Yes. CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalogue on 3 November 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2026-119977?

US federal agencies must remediate it by 6 November 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2026-119977 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 1.2%, the 68th percentile of every CVE it scores.

How do I fix CVE-2026-119977?

Apply the vendor's fix or mitigation; CISA lists only vulnerabilities seen exploited. If you cannot patch now, restrict network access to the affected product. Check for signs of compromise since the date it was added to the list.

Same vendor

Other WordPress vulnerabilities being exploited

CVEProductTypeListed
CVE-2026-87902Coreremote code execution25 September 2026
CVE-2026-60137Coreremote code execution21 July 2026
CVE-2026-63030Coreremote code execution21 July 2026

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.

Chat with us