Black Friday

Your professional website for 360 USD: domain, hosting, maintenance and 2 email accounts included the first year.

No lock-in contract, with real people behind it. We want you to be a happy client.

Give your business its own place on the internet. This is the offer to get started.

See the offer

Critical flaw in the WordPress core: what happened and how to protect your website

Candado cerrado sobre un teclado de ordenador, concepto de ciberseguridad

In recent weeks WordPress has made headlines in the cybersecurity press again, and not because of a questionable plugin: the problem is in the core itself. On October 28, 2026, WordPress 7.1.4 was released to fix a vulnerability affecting versions from 4.7 onward, and the U.S. cybersecurity agency CISA has added it to its catalog of actively exploited flaws.

When something like this goes viral, two equally unhelpful reactions tend to mix: panic (“I’ve been hacked”) and shrugging it off (“it won’t happen to me”). This guide tells you what happened, what real risk your website faces and what to check today. The data is current as of November 11, 2026 and comes from the sources cited at the end.

Quick summary

  • The vulnerability CVE-2026-119977 affects the WordPress core from 4.7 through 7.1.3. It is fixed in 7.1.4.
  • It is exploited during a core update, in a window of a few seconds. Its complexity is high, but automated attempts have been detected.
  • In July there was already another chain of serious core flaws, fixed in 7.0.2. Core flaws exist: what changes is the reaction time.
  • What to do: check the version, verify that the update completed, look for traces and don’t leave maintenance to chance.

What happened

The flaw, cataloged as CVE-2026-119977, is a “race condition” in the core update process. According to SOC Prime’s analysis, it has a CVSS score of 8.1 and in theory allows remote code execution without needing to log in, although with high attack complexity.

The mechanism is simple to understand. When WordPress updates with the full package, it briefly leaves installation files in a temporary folder (wp-content/upgrade), at predictable paths accessible from the internet, including a setup-config.php. If an attacker manages to reach that file while it exists, they can exploit it. The window may last only a few seconds, but automated probes can try thousands of times.

Closed padlock on a computer keyboard, cybersecurity concept
A core flaw affects all WordPress websites equally, regardless of where they come from.

This is the timeline gathered from the sources:

  • October 28: WordPress releases version 7.1.4 with the fix.
  • October 30: the first attempts are observed on decoy systems (honeypots).
  • October 31: the vulnerability’s official record is published.
  • November 6: deadline set by CISA for U.S. federal agencies to apply the fix, after adding it to its catalog of exploited vulnerabilities.

An important nuance: tens of thousands of requests against those paths were reported in the first 24 hours (Wordfence mentioned more than 18,500 in the first 21), but these are attempts, many of them blocked, not compromised websites. It’s a sign of mass scanning, not a count of victims.

It’s not the first time this year

On July 21, 2026, WordPress had already released urgent security versions (7.0.2, 6.9.5 and 6.8.6) to fix two chained flaws, according to the notice from Uruguay’s National Computer Security Incident Response Center:

  • CVE-2026-63030: a path-handling confusion in the REST API batch endpoint.
  • CVE-2026-60137: an SQL injection caused by insufficient sanitization of a WP_Query parameter.

Combined, they allowed unauthenticated SQL injection and then remote code execution on standard installations. The notice states that they were in CISA’s catalog and that public proofs of concept existed; part of the technical press dubbed it “WP2Shell.” WordPress enabled forced automatic updates for the versions that support them.

The practical takeaway from both episodes is the same: the WordPress core is heavily scrutinized software and flaws are fixed quickly, but only the patch that is actually applied protects you.

What real risk your website faces

If your site is on 7.1.4 or later, you’re protected against this specific flaw. Most websites receive core security updates automatically, but there are situations where that doesn’t happen:

  • Hosts or configurations that disable automatic updates.
  • Old sites, test sites or sites on subdomains nobody remembers.
  • Updates that fail halfway (because of permissions, disk space or conflicts) and that nobody verifies.
  • Sites left on unsupported branches: the sources remind us that only the latest version receives active support.

It’s worth putting the risk in context: the vast majority of WordPress vulnerabilities are recorded in plugins and themes, not in the core. A core flaw draws attention precisely because it is rare and affects everyone equally, but day-to-day risk is still in what you install on top. Our guide to the 10 security measures that matter helps you organize it.

What to do today: a checklist

Desk with programming monitors and a tablet showing a task list
A security review works best as a fixed, repeatable checklist.
  1. Check the version. In the WordPress dashboard, go to Dashboard → Updates. It should say 7.1.4 or later (or the equivalent security version for your branch).
  2. Verify that the update completed. Don’t assume it “must have done itself”: confirm the version number on every site.
  3. Take inventory. Test sites, forgotten copies, subdomains and old client sites count too.
  4. Make a recent backup, stored off the server, before touching anything. If you don’t have a clear strategy, the 3-2-1 strategy helps.
  5. Ask your host to check the logs for requests to wp-content/upgrade and setup-config.php, and to restrict web access to that temporary folder if possible.
  6. An application firewall helps, but it doesn’t replace the patch. Use it as an additional layer, not as an excuse for not updating.

How to tell if you’ve already been compromised

Updating fixes the flaw, but it doesn’t remove anything that was already installed before the patch. If your website was on a vulnerable version during the weeks of greatest activity, look for these signs:

  • Administrator users you don’t recognize.
  • New plugins you didn’t install.
  • New or modified PHP files, especially in file upload folders.
  • Strange scheduled tasks or outgoing connections.
  • Odd redirects or spam pages appearing in Google.

If you suspect something, isolate the site, preserve the logs, change the credentials WordPress could access (administrators, database, FTP or SSH) and restore from a clean backup. In our guide to the seven signs your WordPress site needs maintenance you’ll find more clues for catching problems in time.

What if I use Elementor, Bricks or Etch?

This flaw is in the core, so it affects a website built with Elementor, Bricks, Etch or the native editor equally: underneath, they all run on the same WordPress. Choosing one builder or another doesn’t protect you from a core flaw; what protects you is keeping the system updated.

What does depend on you is the attack surface you add on top. Three simple habits help with any builder:

  • Fewer add-ons: every extra plugin is more code to maintain. Uninstall the ones you don’t use.
  • No “nulled” versions: pirated premium plugins or themes are one of the classic routes of infection.
  • Update with a safety net: backup first and, if the site is important, test in a staging environment before going to production.

Frequently asked questions

Is my website hacked if I hadn’t updated?

Not necessarily. The attack requires reaching a temporary file for a few seconds in the middle of an update, and its complexity is considered high. But if your version is earlier than 7.1.4, update as soon as possible and check for signs of compromise.

I have automatic updates turned on. Can I forget about it?

They help a lot, but it’s best to verify that they completed. A permissions failure, a host that blocks them or a forgotten site can leave you on a vulnerable version without your knowing.

Does a security plugin protect me?

It can add a useful layer, such as a firewall or a scanner, but it doesn’t replace updates. The main protection against a known flaw is applying the patch.

How often should I review my WordPress?

At a minimum, a monthly review of version, backups, users and plugins, and an immediate check whenever an important security notice is published. If you don’t have the time, that’s exactly what a maintenance service covers.

Don’t let an urgent update catch you off guard

With S@Y Digital, technical WordPress maintenance is included the first year, along with a design of up to 10 pages, the domain, hosting and two emails, for 360 USD and with no lock-in.