Skip to main content
Defentria

Vulnerabilities

Attackers target a WordPress flaw fixed on 28 October: check that your company website has been updated

WordPress 7.1.4, released on 28 October, fixes a flaw in the update process that can allow code to be run on the website's server. CISA confirmed on 3 November that it is being exploited. If your company has a WordPress website, this is the week to check its version.

By Defentria editorial teamPublished 3 min read

WordPress — Affected software (website content management system)

Half-open laptop on a glass table, with an online shop's page on the screen
Image: Jens Kreuter jenskreuter on Wikimedia Commons (CC0)

In 30 seconds

  • WordPress 7.1.4, released on 28 October, fixes a flaw in the update process that can allow code to be run on the server during an update (CVE-2026-119977).
  • CISA added it to its catalogue of actively exploited vulnerabilities on 3 November.
  • According to Wordfence, attack attempts began within hours of the patch being released: more than 18,500 requests in the first 21 hours.
  • It affects versions 4.7 to 7.1.3. You need to be on 7.1.4 or the fixed version of your branch (for example, 7.0.8 or 6.9.11).

Does this affect me?

It affects you if your company's website or online shop runs on WordPress and hasn't been updated since 28 October. It's common for the website to be managed by an agency or a freelancer and for nobody in the company to know which version it runs: if that's your case, ask this week. If your website doesn't use WordPress, this news doesn't affect you. No Spanish victims have been confirmed.

What happened

On 28 October 2026, WordPress released version 7.1.4, a security update it recommends installing "immediately". The first fix on the list is, in the project's own words, "a weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window".

The next day, security firm Wordfence explained the problem: while WordPress installs a complete update, it temporarily unpacks the new files into a folder with a predictable location that, on many servers, can be reached from the internet. An attacker who arrives at exactly the right moment can use this to run code on the server, with no username or password needed.

On 3 November, the US cybersecurity agency (CISA) added the flaw, tracked as CVE-2026-119977, to its catalogue of actively exploited vulnerabilities.

What we know

  • Affected versions: 4.7 to 7.1.3, according to the vulnerability record published by Wordfence.
  • Fixed versions: 7.1.4 and the equivalents for each branch, such as 7.0.8, 6.9.11 or 6.8.12, according to Wordfence. WordPress announced that it would bring the fix to all branches that still receive security patches, back to 4.7. According to Wordfence, versions 4.6 and earlier no longer receive security updates.
  • Severity: Wordfence gives it a CVSS score of 8.1 (high). Exploiting it is difficult, because the attacker has to hit a window that, in its tests, lasted only seconds. That's why attackers check websites over and over, waiting for them to update.
  • Attacks: Wordfence recorded the first attempt nine minutes after enabling its protection, and more than 18,500 requests targeting the flaw in the first 21 hours.
  • Automatic updates: WordPress says that on sites that support them, the update installs itself.
WordPress logo
WordPress logo. Source: Wikimedia Commons (public domain)

What we don't know yet

  • Whether any attack has succeeded. CISA considers it exploited, but neither CISA nor Wordfence gives details of compromised websites.
  • How many attacks there are. Some media outlets quote Wordfence figures that differ from the ones we have been able to check; we only give those published by Wordfence.
  • Whether there are victims in Spain. None have been confirmed.

Why it matters

The website is the company's shop window and, when it's an online shop, its till as well. An attacker who runs code on the server can change pages, slip in fraudulent links or access the customer data stored by the website.

This flaw also has a particular twist: the moment of risk is precisely the update. That's no reason to stop updating, but a reason to do it as soon as possible and get off the vulnerable versions.

What it means for an SME

Many SME corporate websites and online shops are built with WordPress. And many of them were set up by an agency or a freelancer who may no longer maintain them. In practice:

  • nobody in the company knows which version of WordPress the website runs;
  • automatic updates are sometimes switched off "so nothing breaks";
  • the website may have been running for years without anyone logging into the admin panel.

What your company should do this week

  1. Check the version. In the WordPress panel, under "Dashboard → Updates", it should show 7.1.4 or the fixed version of its branch. If you can't log in, ask whoever maintains the website.
  2. If it isn't up to date, ask for it to be updated now, and for automatic security updates to be switched on.
  3. If the website was on version 4.6 or earlier, it no longer gets patches: ask for a plan to migrate it to a supported version.
  4. If it went without updating these past few days, ask for a review: admin users nobody recognises, plugins nobody installed or unfamiliar files on the server.
  5. Make sure there's a recent backup of the website and that someone has checked it can be restored. Our guide to backups (in Spanish) explains how to organise them.

Sources

  1. WordPress.org — «WordPress 7.1.4» (28 October 2026)Primary source
  2. CISA — Known Exploited Vulnerabilities (KEV) catalogue: CVE-2026-119977, added on 3 November 2026Primary source
  3. Wordfence — «WordPress 7.1.4 Patches Unauthenticated Upgrade-Window RCE; Exploitation Attempts Detected After Release» (29 October 2026)

Defentria editorial team. The Defentria team selects cybersecurity news from primary sources (CERTs, official bodies and vendors) and explains what it means for a Spanish SME and what to do about it.