WordPress 7.1.4: The Upgrade-Time Remote Code Execution Flaw (CVE-2026-119977) Is Being Exploited, What to Do
WordPress 7.1.4 fixed a race-condition flaw in the core upgrade process (CVE-2026-119977). CISA added it to its exploited list on 3 November; Wordfence said it blocked more than 13,000 attacks in a single day.
In brief: CVE-2026-119977 is a TOCTOU race condition in the WordPress core upgrade process. According to BleepingComputer, attackers can exploit predictable, web-accessible staging paths used during full-package core upgrades to execute code on the server without authentication; the attacks are high-complexity but exploitation is ongoing. The flaw was found by Umut Bayram of Picus Security. The fix arrived in WordPress 7.1.4 on 28 October 2026, and CISA added it to its Known Exploited Vulnerabilities (KEV) catalog on 3 November. Wordfence said it blocked 13,095 attacks targeting the flaw in the past 24 hours. What to do: update WordPress to 7.1.4 (or newer). This article is based on BleepingComputer's report.
Last updated: 9 November 2026
What happened?
The WordPress core upgrade mechanism temporarily exposes files in predictable directories reachable from the web during full-package updates. As the report describes it, an attacker can exploit a race condition during the update to run code on the server. This is a TOCTOU (time-of-check time-of-use) bug: something is checked as safe, but can be changed just before it is used.
| Item | Detail |
|---|---|
| Identifier | CVE-2026-119977 |
| Type | TOCTOU race condition in the core upgrade process |
| Impact | Unauthenticated remote code execution (high attack complexity) |
| Fix | WordPress 7.1.4 (28 October 2026) |
| CISA KEV | 3 November 2026 (evidence of exploitation) |
| Exploitation evidence | Wordfence: 13,095 blocked attacks in the past 24 hours |
| Discovered by | Umut Bayram, Picus Security |
The BleepingComputer report does not state the affected version range clearly; treat every version before 7.1.4 as affected. Severity may also be scored differently by different sources (the report says “high”); evidence of exploitation matters more for priority than the score.
Why does a flaw that appears only “during an update” matter so much?
A few reasons:
- The window is short but predictable: upgrades run at known times and can run automatically; because the directory names are predictable, an attacker can try to catch the moment.
- No authentication needed: nobody has to create an account or log in to your site.
- Exploitation has started: a CISA KEV entry is not a theoretical threat but proven use. CISA's federal deadline was 6 November; that mandate applies only to federal agencies, but CISA urged all defenders to prioritise patching.
- WordPress is a frequent target: for July's “wp2shell” chain (patched in 7.0.2; CVE-2026-63030 and CVE-2026-60137), public exploits appeared one day after the patch and were used in September to steal more than 18,500 records. WordPress core flaws can be weaponised quickly.
If your site runs WordPress: 8 steps
- Find your version: Dashboard > Updates in the admin, or
wp core version. - Update to 7.1.4 (or newer). Even if automatic updates are on, verify the version: failed updates can be silent.
- Take a backup: files and database before updating, with a rollback plan.
- Plan a maintenance window: update when traffic is low if you can, and watch it finish.
- Look for suspicious traces: unexpected new files (
wp-content,wp-admin, the root), admin users you don't recognise, modified core files.wp core verify-checksumsverifies core files. - Use a firewall/WAF: tools like Wordfence showed they can block attacks on this flaw; a WAF does not replace the patch.
- Update plugins and themes too: plugin flaws are exploited as often as core flaws. Remove unused ones.
- Consider rotating secrets: if you suspect compromise, admin passwords, the database password, and the keys and salts in
wp-config.php.
If you run other PHP applications on the same server, check the PHP2Shell patches too.
WordPress or something else?
This article is not about disparaging WordPress: being the world's most common CMS, it also takes the most attacks. This is a question of maintenance load: every core, plugin and theme update is a responsibility. We covered which structure fits which need in our WordPress vs Next.js comparison and our tech stack guide. Whatever you choose, without a maintenance and SLA arrangement a security flaw becomes inevitable sooner or later.
Maintenance with Aktaş Digital
To keep your existing WordPress site up to date, harden it or move to a lower-maintenance structure, use our quote form. Related services: web applications.
Frequently Asked Questions
My automatic updates are on. Should I still do something?
Check your version. Automatic updates apply minor releases on most sites, but may not have applied because of an error or configuration. You should see 7.1.4 or later in the admin.
How do I know whether my site was hacked through this flaw?
Unexpected files, admin accounts you don't recognise, modified core files or unusual outgoing traffic can be signs. Core file verification and server logs are the first checks. If in doubt, get help from a specialist.
It's only a risk during an update, so isn't postponing the update safer?
No; the flaw sits in versions before 7.1.4 and is being exploited. Moving to the fixed version closes the risk; postponing prolongs the window.
My host updates automatically. Am I still responsible?
Managed WordPress hosting often updates core, but verifying the version and looking for traces is still your responsibility. Ask your host for written confirmation.
Does this flaw affect WordPress.com too?
The source report does not say. Check the WordPress installations you run on your own server or hosting, and follow your platform provider's announcements.
Conclusion
With CISA-confirmed exploitation, CVE-2026-119977 needs an urgent core update. Move to 7.1.4, verify the version and check for signs of compromise. The first step: open your WordPress admin, take a screenshot of the version and send it to your software team.
