WordPress core RCE vulnerability exploited within 24 hours, urgent update required
A high‑severity WordPress core RCE flaw is being actively probed; update to 7.1.4 and monitor the upgrade directory immediately.
If your business relies on WordPress to power its website, a new remote code execution (RCE) risk has emerged that attackers are already probing. The flaw affects sites running WordPress core versions 4.7 up to 7.1.3 and carries an 8.1 score on the Common Vulnerability Scoring System, indicating a serious threat.
The problem originates from staging directories that become web‑accessible during full‑package core upgrades. When WordPress unpacks an update, it creates a predictable path under wp‑content/upgrade. An attacker who can reach that path at the right moment can upload a malicious PHP file and obtain full control of the site. Exploitation requires a very narrow window while the upgrade is in progress, public web and PHP access to the staging tree, and a predictable filename such as setup‑config.php.
Wordfence, a widely used WordPress security service, reported that it blocked 62 969 attempts to hit those paths in the first 24 hours after the flaw was disclosed. Two of the largest sources of traffic repeatedly probed small groups of sites for roughly 14.5 hours, behaviour that matches the brief upgrade window attackers need.
WordPress released a patch on 28 October 2026 in version 7.1.4. The advisory from the WordPress security team stresses two immediate actions:
- Upgrade every WordPress installation to 7.1.4 without delay.
- Monitor the wp‑content/upgrade directory for unexpected PHP requests and watch for unfamiliar administrator accounts, plugins or stray PHP files.

Photo by Christina Morillo on Pexels
Below is a concise reference that maps each confirmed fact to its source claim.
| Fact | Detail |
|---|---|
| High‑severity RCE flaw | Impacts WordPress core 4.7, 7.1.3 (claim fa720c22) |
| CVSS score | 8.1 (claim 1058056d) |
| CVE identifier | None assigned (claim d65f5ddd) |
| Patch release | WordPress 7.1.4 on 28 Oct 2026 (claim 2bf9d6a9) |
| Cause | Predictable, web‑accessible staging paths during full‑package upgrades (claim 0e195dda) |
| Exploitation window | Requires narrow moment while core is unpacking, with public web/PHP access to staging directory (claim 25adb288) |
| Attack pattern | Polling of paths such as "setup‑config.php" (claim 41e1a33e) |
| Blocked attempts | 62 969 attacks in first 24 h (claim ebb526f8) |
| Large‑source behaviour | Two sources polled sites for ~14.5 h, matching upgrade window (claim aa9570f6) |
| Recommended actions | Update to 7.1.4 and monitor staging directory and admin accounts (claim c294073e) |
What you should do right now
- Log in to your WordPress admin dashboard and check the installed version. If it is below 7.1.4, schedule the update immediately.
- After updating, inspect the wp‑content/upgrade folder for any PHP files that were not created by the upgrade process.
- Review the list of users with Administrator role; remove any accounts you cannot recognise.
- Scan installed plugins for unexpected files or recent additions.
By acting swiftly, you close the narrow window that attackers are trying to exploit and reduce the risk of a full site compromise.
Terms used in this article
- Remote code execution (RCE), a vulnerability that lets an attacker run arbitrary code on a server from a remote location.
- CVSS, Common Vulnerability Scoring System, a numeric rating that reflects the severity of a security flaw.
- Staging directory, a temporary location where WordPress unpacks update files before they are moved into place.