CVE-2026-119977 affects WordPress (core) — CMS. The flaw can be exploited without an account, but the CVE record does not say what it lets an attacker do.
Who is affected?
- Product: WordPress (core) — CMS
Is this flaw being exploited?
Yes. The KEV catalog of CISA, the US cybersecurity agency, lists it among the flaws seen exploited, since November 3, 2026. CISA set November 6, 2026 as the deadline for US government agencies to fix it.
What to do
Deal with this now: the record names no fixed version: check on the vendor's page that a version later than 7.1.3 is out. Check which version of WordPress (core) runs on your site, then apply the update.
Technical details
- Identifier: CVE-2026-119977
- Severity: 8.1 (High, CVSS 3.1)
- Affected versions: 4.7.0 to 4.7.38, 4.8.0 to 4.8.33, 4.9.0 to 4.9.34, 5.0.0 to 5.0.30, 5.1.0 to 5.1.27, 5.2.0 to 5.2.29, … (25 in total)
- Fixed version: not given in the CVE record
Sources:
- NVD entry CVE-2026-119977
- CISA KEV catalog: entry added on November 3, 2026
- Vendor advisory (core.trac.wordpress.org, class-core-upgrader.php#L162)
- Vendor advisory (core.trac.wordpress.org, class-wp-upgrader.php#L378)
- Vendor advisory (core.trac.wordpress.org, update-core.php#L1549)
- Selected in the roundup of the Week 45 · November 2–8, 2026
- Data checked on November 13, 2026