CVE-2026-119977: WordPress Core flaw exploited in the wild, what we know

WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.

• Severity: HIGH (CVSS 3.1 8.1, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
• Weakness: CWE-367.
• NVD published 2026-10-31, status Deferred.

Anyone running WordPress Core. Internet-facing instances are the priority.

NVD has not published affected version ranges for this CVE yet. Use the vendor advisory in the sources below to confirm which builds are affected.

• Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-11-03; federal remediation due date 2026-11-06.

CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog on 2026-11-03. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs WordPress Core, put this at the top of the patch list. CISA gave US federal agencies until 2026-11-06 to deal with it, and that is a sensible deadline for a small business too.

• Patch. Install the latest update from WordPress. NVD does not list a fixed version, so the vendor advisory linked on this page is the reference for which release closes it.
• If you cannot patch yet. Follow CISA's 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.
• Check your exposure. Find out whether WordPress Core can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
• When to call IT support. Call your IT support provider now if you run WordPress Core and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

• EPSS (probability of exploitation activity in the next 30 days): 0.60%, higher than 49% of all scored CVEs (as of 2026-11-03).
• CVERadar threat level: 56/100 (see methodology).
• Likely ATT&CK techniques: T1203 Exploitation for Client Execution (inferred); T1190 Exploit Public-Facing Application (inferred).

1. Find every instance. List where WordPress Core runs, including test, DR and forgotten internet-facing systems, and record the installed version.

   # Core version, then every plugin with its installed and available version
   wp core version
   wp plugin list --fields=name,status,version,update_version

2. Apply the latest vendor update. NVD does not list a fixed version, so follow the vendor advisory for the patched release.

   # Update the affected plugin (use the slug from `wp plugin list`)
   wp plugin update <plugin-slug>
   
   # Or, if the advisory is about WordPress core
   wp core update

3. If you can't patch today, follow CISA's 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.
4. Verify the fix. Re-run the version check above on every instance and confirm it reports the fixed build. Re-scan from outside if the service is exposed.
5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

• T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to WordPress Core (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-10-31.
• T1203 Exploitation for Client Execution: Exploitation of client or server software usually shows as crashes of the affected process followed by unexpected child processes; check EDR alerts for both.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

• NVD: CVE-2026-119977 nvd.nist.gov/vuln/detail/CVE-2026-119977
• CVE.org record www.cve.org/CVERecord?id=CVE-2026-119977
• Vendor link from CISA KEV wordpress.org/news/2026/10/wordpress-7-1-4
• Vendor link from CISA KEV www.wordfence.com/threat-intel/vulnerabilities/wordpress-core/wordpres
• CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
• FIRST EPSS (2026-11-03) api.first.org/data/v1/epss?cve=CVE-2026-119977