CVE-2026-119977 WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition
Exploited in the wild
High 8.1
Published
Updated
Check this codebase for CVE-2026-119977 and fix it if it is affected.
What it is: CVE-2026-119977 is a high-severity vulnerability in WordPress, published on 31 Oct 2026.
Exploitation: Yes. Attackers have exploited CVE-2026-119977 in the wild since at least 3 Nov 2026.
Affected product: WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-119977/ (Markdown: https://insights.sbomify.com/CVE-2026-119977/index.md)
- Exploited in the wild
- Since 3 Nov 2026
- Fix
- Available
What is CVE-2026-119977?
CVE-2026-119977 is a high-severity vulnerability in WordPress, published on 31 Oct 2026.
Official description
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.
Weakness: CWE-367
Which versions are affected by CVE-2026-119977?
It affects 1 product.
Products include WordPress.
How do I fix CVE-2026-119977?
Upgrade to a fixed version. US federal agencies must fix it by 6 Nov 2026.
Is CVE-2026-119977 being exploited?
Yes. Attackers have exploited CVE-2026-119977 in the wild since at least 3 Nov 2026.
Public exploit code: 9 proofs of concept on GitHub.
Other vulnerabilities in WordPress
- CVE-2026-63030 WordPress Core Interpretation Conflict
- CVE-2026-87902 WordPress Core Remote File Inclusion
- CVE-2026-60137 WordPress Core SQL Injection
- CVE-2012-2399 Cross-site scripting (XSS) vulnerability in swfupload.swf in SWFupload 2.2.0.1 and earlier, as used in WordPress before 3.5.2, TinyMCE Image
- CVE-2012-2400 Unspecified vulnerability in wp-includes/js/swfobject.js in WordPress before 3.3.2 has unknown impact and attack vectors.
Sources
Also known as DEBIAN-CVE-2026-119977, GHSA-p6jj-qrp3-7m4g.