Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

WordPress 7.1.4 Security Update: What Site Owners Should Check

WordPress 7.1.4 fixes 22 flaws, including CVE-2026-119977, an update-window RCE now in CISA KEV. What to check and patch.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
30 October 2026
Updated
19 November 2026
Reading time
6 min read
Open glass doorway outlined by coral red light

WordPress 7.1.4 is a security release that fixes 22 vulnerabilities, according to the release documentation. The most serious is a weakness in the core update process that could lead to remote code execution during an upgrade. Wordfence reports exploitation attempts against it since shortly after the release, so site owners should update without delay.

Advisory
Severity HighStatus Update Available
WordPress 7.1.4 Security Release
Review your installed version and follow the official update instructions.
Published
2026-10-28 UTC
Updated
2026-11-04 UTC
For
WordPress Site Owners
Sharing
TLP:CLEAR

Last checked against sources: November 4, 2026.

Update 4 November

CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog on November 3, 2026, with a due date of November 6. CISA lists ransomware campaign use as Unknown. CVE.org now shows a published record for it, with Wordfence as the CNA. Our CVE-2026-119977 vulnerability page lists the affected and fixed version for each branch.

Update 31 October

Wordfence’s vulnerability entry shows a rolling count of attacks it blocked in the previous 24 hours. The count read 70,095 on October 30 and 60,471 on October 31. Wordfence also lists the flaw as CVE-2026-119977, but CVE.org had no published record on October 31. The flaw is still not in the CISA KEV catalog.

What Changed in the Update Process?

The WordPress release note describes a weakness that may lead to remote code execution during the upgrade window. The companion documentation calls it a race condition during core updates. Those descriptions define the update period as the context. They do not describe an attack against every site at all times.

The official release note credits the researcher who reported the weakness. It does not give a CVE identifier or an attack walkthrough for this item, and WordPress itself does not say whether the weakness has been exploited. Wordfence now lists CVE-2026-119977, but CVE.org returned no published record on October 31. The flaw was not in the CISA KEV catalog as of that date.

Are Attackers Already Trying to Exploit It?

Wordfence says the flaw affects WordPress 4.7 through 7.1.3 and rates it CVSS 8.1. It needs no login, but attack complexity is high: an attacker must win a race, and in the Wordfence lab the window normally lasted only seconds.

Wordfence deployed a firewall rule on October 28 at 20:30 UTC and saw the first match nine minutes later. In the first 21 hours it counted more than 18,500 requests targeting staged setup-config.php installer paths. Two of the largest sources polled small groups of sites for about 14.5 hours, which Wordfence links to catching the upgrade window. Not every request used the exact vulnerable path.

The Wordfence vulnerability entry carries a rolling count of attacks its firewall blocked in the past 24 hours. On October 30 at 16:55 UTC it showed 70,095. On October 31 at 05:17 UTC it showed 60,471. Press reports of nearly 63,000 attacks appear to quote the same counter at another moment.

Wordfence calls this exploitation attempts and, as of October 31, had not reported confirmed compromises. A blocked attack is not a successful one. Treat the activity as a reason to patch now, not as proof that a given site was breached.

Other Security Fixes in 7.1.4

The release addresses several stored cross-site scripting issues. These include issues involving block markup and the personal data erasure request screen. The detailed documentation describes the role needed for some of those issues, so administrators should read each entry separately.

WordPress also lists a stored denial-of-service issue in the Interactivity API. Another issue could allow unauthenticated visitors to discover unpublished Customizer changes. These are separate findings and should not be described as the same remote code execution weakness.

The release includes an update to bundled root certificates following the eMudhra revocation. That certificate update has its own purpose and is not proof of a compromise of a WordPress site. The project recommends the security release for site owners.

Which Versions Should Teams Check?

WordPress says the 7.0 and 6.9 branches are affected by all 22 issues, while older branches are affected by fewer. It says security fixes are backported to eligible branches through 4.7. The original release announcement described those backports as in progress. The project also says only its most recent version is actively supported.

The official release archive now lists a patched release for every branch from 4.7 to 7.1, all dated October 28. On October 31, the WordPress.org update service offered each of them as an automatic update. Wordfence lists the same 25 patched versions, from 4.7.39 to 7.1.4. Sites on 4.6 or earlier get no fix and need a supported release.

Plan the Update and Verify It

WordPress points administrators to Dashboard > Updates or the official download. Sites that support automatic background updates may begin that process automatically. Wordfence advises checking the installed version rather than assuming a background update finished. The official repository also has the 7.1.4 release tag and the readme for that version.

Update Checklist
  1. InventoryList the core version for each site.
  2. Check the branchRead the matching official release.
  3. Plan the changeConfirm the recovery path and update window.
  4. VerifyCheck the installed version after the update.

Wordfence says the fix randomizes the staging directory, adds an index guard and blocks unsafe promotion of staged configuration data. For sites that stayed unpatched, Wordfence advises looking for unexpected requests to PHP files under wp-content/upgrade, unfamiliar administrator accounts, unexpected plugins, or PHP files you did not place there.

Wordfence says the exploit requests a staged PHP file directly, without first loading WordPress. Logging that runs inside WordPress may therefore miss it, so check the web server access log as well. Look for requests to setup-config.php or other PHP files under wp-content/upgrade. Wordfence has not published attacker IP addresses or user agents for this activity.

Inventory the WordPress core version across the sites you manage, and treat the update window as attack surface, as our DevOps security checklist explains. Coordinate update timing with site owners and confirm a usable recovery path before making changes. Review plugins and themes separately, since this announcement concerns the WordPress core release.

Our vulnerability management guide covers tracking owners and fixes. For the broader category, the cross-site scripting explanation describes the risk behind several listed fixes. The earlier WordPress core RCE analysis covers a different set of vulnerabilities and should not be treated as this update flaw.

Evidence and Uncertainty
Exploit signals
  • Official fixYesWordPress describes an update-window weakness fixed in this release and in backports to 4.7.2026-10-28
  • Exploitation attemptsYesWordfence counted 60,471 blocked attacks in 24 hours; it has not reported confirmed compromises.2026-10-31
  • CVE recordYesCVE-2026-119977 is published on CVE.org, with Wordfence as the CNA.2026-11-04
  • CISA KEVYesAdded November 3, 2026 with a due date of November 6; ransomware use is marked Unknown.2026-11-03
Verdict Patch Now and Check Server Logs

Plugins need the same attention as core. Contact Form 7’s CVE-2026-114432 is an unauthenticated file upload flaw, fixed in version 6.2.4.

Plugins need the same attention as WordPress core. CVE-2026-119506 lets an unauthenticated visitor escalate privileges in the Frontend Admin by DynamiApps plugin, fixed in 3.30.2.

A configured AutomatorWP Pro Webhooks workflow may also permit account password resets on versions through 1.4.4. Check the CVE-2026-126173 Webhooks profile for the exact automation condition and fixed version.

If you also run the WP Duplicate plugin, the CVE-2026-123751 response workflow explains the separate plugin-removal and host-review decision.

WordPress published a separate WordPress 7.1.5 security update on November 18, 2026, with 20 core fixes.

Frequently Asked Questions

What does WordPress 7.1.4 address during core updates?

WordPress describes an update-process race condition that could lead to remote code execution during the upgrade window.

Are fixes available on older WordPress branches?

WordPress backported the security fixes to every eligible branch through 4.7. The release archive lists patched versions from 4.7.39 to 7.1.4, all dated October 28; versions 4.6 and earlier get no fix.

Is the WordPress 7.1.4 flaw being exploited?

Wordfence reports exploitation attempts since October 28 against WordPress 4.7 through 7.1.3. Its rolling count showed 60,471 blocked attacks in 24 hours on October 31, and as of that date it had not reported confirmed compromises. CISA added the flaw to its KEV catalog on November 3, 2026.

How can I check whether my site was targeted?

Search the web server access log for requests to setup-config.php or other PHP files under wp-content/upgrade. Wordfence also advises checking for unfamiliar administrators, unexpected plugins and PHP files you did not add.

Sources

  1. WordPress 7.1.4 security release
  2. WordPress 7.1.4 release documentation
  3. WordPress release archive
  4. Wordfence: WordPress 7.1.4 upgrade-window RCE and exploitation attempts
  5. Wordfence Intelligence: WordPress Core 4.7.0 - 7.1.3 upgrade-window RCE entry
  6. CISA Known Exploited Vulnerabilities Catalog
  7. CVE-2026-119977 CVE record
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →