WordPress Core Vulnerability Exploited: CISA Confirms Attacks Through CVE-2026-119977
This time the flaw is not in a plugin you can uninstall but in WordPress itself, and it is already being used in real attacks. If you run a site, the order matters: update, review your logs and keep watching.


On this page
Most security advisories about WordPress concern plugins, but this time it is a WordPress core vulnerability exploited in the platform itself. CISA (the Cybersecurity and Infrastructure Security Agency, the US cybersecurity agency) added it on 3 November 2026 to its Known Exploited Vulnerabilities catalogue on evidence of active exploitation [1].
Because patches have been available since late October, finding the fix is not the problem. The problem is order and speed: first update, then check whether someone got in before the patch.
CISA confirms that a WordPress core flaw is being exploited
CISA's notice is brief. It identifies the flaw as CVE-2026-119977, a TOCTOU race condition in WordPress Core, and explains that it is adding it to the KEV (Known Exploited Vulnerabilities) catalogue because there is evidence it is being exploited [1]. The agency adds a general warning: this type of vulnerability is a frequent attack vector and poses significant risks [1].
The technical context comes from the report The Hacker News published on 4 November. According to The Hacker News, the flaw has a CVSS score of 8.1, is considered high severity and could be used to execute arbitrary code on affected servers [2]. The same report states that the patches were released in late October [2].
The two signals reinforce each other. The report rates this vulnerability as high severity. Its entry in CISA's catalogue says something different: that someone is already trying to take advantage of it. With a fix available as well, deciding what to do is simple. The hard part is doing it in time.
A TOCTOU race condition explains why the risk sits in the core and not in a plugin
TOCTOU stands for time-of-check to time-of-use. It is like checking that a door is closed and, a few seconds later, acting as if it were still closed without looking again.
The CISA description reproduced by The Hacker News specifies where that gap lies. According to that description, the flaw could let unauthenticated attackers execute code on the server during the update window. The cause is predictable, web-accessible staging paths used in full core updates [2]. The same outlet reports that, according to Wordfence, exploiting it does not require an account on the site. It does require taking advantage of a brief interval during a full WordPress Core update [2].
This is where the paradox appears. The moment of exposure coincides with a full core update. CISA says to apply mitigations following the vendor's instructions, or to stop using the product if no mitigations are available. Before you update WordPress core, check the vendor's instructions on the process. That is why it is worth following the official WordPress advisory to the letter. If you want to understand how flaws like this are found in a service exposed to the internet, you can read up on how to detect vulnerabilities in a web application.
Exploitation attempts appeared around the time the patch was published
The data gathered by The Hacker News allows a short timeline to be drawn. It shows how quickly malicious activity appeared:
| Date | What happened | Source |
|---|---|---|
| Late October 2026 | Patches published | The Hacker News [2] |
| 30 October 2026 | Previdian observes exploitation events against its honeypot | The Hacker News [2] |
| First 21 hours after disclosure | Wordfence records more than 18,500 requests against setup-config.php installer paths | The Hacker News [2] |
| 3 November 2026 | CISA adds the flaw to the KEV catalogue | CISA [1] |
| 6 November 2026 | Deadline for US federal civilian agencies to apply the fixes | The Hacker News [2] |
According to the same report, 12,632 attacks attempting to exploit the flaw had been blocked in the 24 hours before its publication [2]. The Hacker News also reports that the attempts recorded by Previdian's honeypot came from an IP address geolocated in the United Kingdom [2].
These figures need to be read with care. The report covers requests recorded by Wordfence, attempts observed by Previdian and a count of blocked attacks. They refer to requests and exploitation attempts, not to a count of compromised sites. What they do allow us to say is that exploitation started early and relied on one very specific path, setup-config.php. That detail will be useful later, when reviewing logs.
The KEV catalogue is a prioritisation criterion even if its deadline is not yours
The KEV catalogue is the public list in which CISA gathers vulnerabilities with observed exploitation. To be included, a flaw needs a CVE (Common Vulnerabilities and Exposures) identifier, evidence of exploitation and clear guidance for mitigating it [1]. That is why a KEV entry carries more weight than an isolated CVSS score: it is no longer a theoretical risk.
CISA ties the catalogue to Binding Operational Directive BOD 26-04, "Prioritizing Security Updates Based on Risk". This directive requires FCEB agencies to prioritise rapid remediation of high-risk KEV vulnerabilities on publicly exposed assets that allow full control after exploitation, and to defer action on lower-risk vulnerabilities. The directive also sets expectations for when those agencies must check whether a system was compromised before the patch was applied [1]. For this flaw, according to The Hacker News, their deadline was 6 November 2026 [2].
That obligation does not extend to a Spanish company, and CISA itself notes that the directive applies only to those federal agencies. Even so, the agency encourages all organisations to manage vulnerabilities according to their risk and to give priority to those in the catalogue [1]. For a small business or a professional who maintains their own website, the federal deadline works as a benchmark of urgency: if a government agency is given days, it makes no sense to leave it for next quarter. If you are looking for a broader framework to order these priorities, the basic cybersecurity guide for SMEs is a good starting point.
The catalogue entries include fields that help refine the decision. One indicates whether the flaw is known to be used in ransomware campaigns. Another indicates whether BOD 26-04 requires forensic triage [3]. In the entry for CVE-2026-119977, use in ransomware campaigns is listed as "Unknown" and the forensic triage required by BOD 26-04 is listed as "Yes". It is worth checking them directly in the catalogue.
The sensible order is to update first, review afterwards and keep watching in the meantime
Based on what the sources say, the reasonable sequence for anyone who administers a WordPress site is this:
- Update the core to the fixed version. Confirm the fixed version in the vendor's official instructions. Check the official WordPress advisory and follow its instructions for the update process.
- Review the server logs. Look for requests to installer paths such as setup-config.php, which according to the Wordfence data reported by The Hacker News is the target of the attacks [2]. Pay particular attention to dates close to any full core update carried out since late October.
- Do not treat a suspicion as closed without analysing it. Do not confuse generic signs of a WordPress compromise with indicators specific to exploitation of this CVE. If you find suspicious requests or have doubts, consider a deeper analysis or consult a specialised team.
- Keep monitoring during the exposure window. Review logs and site integrity regularly while exploitation remains active.
There is one important nuance. Updating closes the door, but it does not prove that nobody came in before. According to The Hacker News, exploitation was already observed on 30 October [2]. BOD 26-04 itself contemplates checking whether there was a compromise before the patch [1]. Organisations without dedicated staff may consider turning to specialised support for that review. For that review, you can consider a specialised service and confirm the scope of its monitoring and analysis.
With a core flaw, exposure is measured in days and not in quarters
This case leaves a simple idea. Here, the sources place the vulnerability in WordPress Core and state that patches exist. It is resolved by updating as soon as possible and checking in the logs whether someone got there before the patch. Between learning of the advisory and acting on it lies almost all of the risk, and in this case that distance is counted in days.
For anyone who maintains a corporate or professional website without a security team behind them, the lesson goes beyond this CVE. Knowing which version of WordPress is running, which parts of the site are exposed to the internet and who reviews the logs is a recurring task, not a one-off reaction to each headline. If you want to check your real exposure with controlled tests, you can consider pentesting to verify the exposure of your website as a next step.
Sources
- CISA Adds One Known Exploited Vulnerability to Catalog — CISA, 2026-11-03
- CISA Confirms Hackers Exploiting WordPress Core Flaw During Software Upgrades — The Hacker News, 2026-11-04
- Known Exploited Vulnerabilities Catalog — CISA
Was this article useful?

Gorka Gonzalo
Founder & CEO
Founded Hodeitek in 2023 and runs the company, after more than 8 years in pentesting, Red Team, OT/ICS auditing, and SOC leadership. A cybersecurity and AI expert, he sets the technical and product direction of HodeiShield and personally leads the most critical engagements — from defense strategy to applying AI in threat detection. He is the client's direct point of contact: whoever scopes the work also answers for the result.