{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2026-119977 in the wild since at least 3 Nov 2026.","exposure":"","fix":"Upgrade to a fixed version. US federal agencies must fix it by 6 Nov 2026.","what":"CVE-2026-119977 is a high-severity vulnerability in WordPress, published on 31 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119977 and fix it if it is affected.\n\nWhat it is: CVE-2026-119977 is a high-severity vulnerability in WordPress, published on 31 Oct 2026. \nExploitation: Yes. Attackers have exploited CVE-2026-119977 in the wild since at least 3 Nov 2026.\n\nAffected product: WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-119977/ (Markdown: https://insights.sbomify.com/CVE-2026-119977/index.md)","id":"CVE-2026-119977","markdown":"https://insights.sbomify.com/CVE-2026-119977/index.md","name":"CVE-2026-119977","record":{"aliases":["DEBIAN-CVE-2026-119977","GHSA-p6jj-qrp3-7m4g"],"analysis":null,"analysis_generated_by":null,"assigner":"Wordfence","cpe":[{"name":"WordPress","product":"wordpress","vendor":"wordpress"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2021-11-15","github_poc":9,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-11-04T18:16:40Z","kind":"github_poc","ref":"https://github.com/Worthes/CVE-2026-119977-WordPress-Upgrade-RCE-Bypasses-7.1.4","stars":6,"title":null},{"date":"2026-11-05T16:40:50Z","kind":"github_poc","ref":"https://github.com/tc4dy/CVE-2026-119977-Toolkit","stars":6,"title":"CVE-2026-119977 – WordPress Core Upgrade-Window RCE (CVSS 8.1) | Red/Blue Team Toolkit. Predictable staging dir takeover, wp-config.php promotion, Bait MySQL proof, WAF origin discovery, rate-limited race oracle, admin shell deploy, version triage. Async, CI-tested. Only ethical \u0026 authorized use, stay legal."},{"date":"2026-11-04T10:12:28Z","kind":"github_poc","ref":"https://github.com/lysophavin18/CVE-2026-119977","stars":5,"title":null},{"date":"2026-11-08T13:25:19Z","kind":"github_poc","ref":"https://github.com/BugStealers/CVE-2026-119977","stars":2,"title":null},{"date":"2021-11-15T10:38:16Z","kind":"github_poc","ref":"https://github.com/paulmann/Bash_WP-CLI_Update","stars":1,"title":"Bash + WP-CLI maintenance for fleets of WordPress sites: core, plugin and theme updates, backups with a restore path, JSON reports, CVE-2026-119977 assessment and hardening."},{"date":"2026-11-08T11:14:07Z","kind":"github_poc","ref":"https://github.com/mehmet-emir-eroglu/CVE-2026-119977","stars":1,"title":"Read-only local WordPress version assessment for CVE-2026-119977."},{"date":"2026-11-04T04:15:42Z","kind":"github_poc","ref":"https://github.com/foxcornlab/wordpress-core-scanner","stars":0,"title":"Detection-only local triage scanner for CVE-2026-119977 (CISA KEV 2026-11-03) in WordPress Core: grades versions 4.7-7.1.3 against per-branch fixes (7.1.4 and backports) and flags wp-content/upgrade exposure. No payloads, no remote probing."},{"date":"2026-11-07T05:40:08Z","kind":"github_poc","ref":"https://github.com/riabinov/CVE-2026-119977","stars":0,"title":null}],"tier":"exploited"},"has_fix":true,"headline":"WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition","id":"CVE-2026-119977","indexable":true,"kev":{"dateAdded":"2026-11-03","dueDate":"2026-11-06","knownRansomwareCampaignUse":"Unknown","product":"WordPress Core","requiredAction":"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.","vendorProject":"WordPress","vulnerabilityName":"WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"wordpress:wordpress","products":["wordpress:wordpress"],"type":null,"year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Flowise through 3.1.4 Custom Function Sandbox Escape RCE via LocalFileStore","id":"CVE-2026-119978"},"nickname":null,"packages":[],"prev":{"headline":"Visual Studio Code GitHub Pull Requests and Issues Extension Information Disclosure Vulnerability","id":"CVE-2026-119976"},"products":["WordPress"],"published":"2026-10-31","related":[{"cvss_score":9.8,"headline":"WordPress Core Interpretation Conflict","id":"CVE-2026-63030","kev_date_added":"2026-07-21","published":"2026-07-17"},{"cvss_score":8.1,"headline":"WordPress Core Remote File Inclusion","id":"CVE-2026-87902","kev_date_added":"2026-09-25","published":"2026-09-22"},{"cvss_score":5.9,"headline":"WordPress Core SQL Injection","id":"CVE-2026-60137","kev_date_added":"2026-07-21","published":"2026-07-17"},{"cvss_score":10,"headline":"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","id":"CVE-2012-2399","kev_date_added":null,"published":"2012-04-21"},{"cvss_score":10,"headline":"Unspecified vulnerability in wp-includes/js/swfobject.js in WordPress before 3.3.2 has unknown impact and attack vectors.","id":"CVE-2012-2400","kev_date_added":null,"published":"2012-04-21"},{"cvss_score":10,"headline":"Unspecified vulnerability in WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 has unknown impact and attack vectors related to \"Media securi","id":"CVE-2011-3122","kev_date_added":null,"published":"2011-08-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-11-04","vendors":["WordPress Foundation"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119977/"}