Padideban
Sign in Download Padideban
How-to guides

WordPress 7.1.4 security update: CISA confirms attacks, check your site now

CISA says a WordPress core flaw (CVE-2026-119977) is being exploited. Here's what WordPress 7.1.4 fixes and how to confirm your site is updated in 5 minutes.

Teal shield icon with a globe and a Version 7.1.4 label, illustrating a WordPress security update
In this post
  1. What happened
  2. Who is at risk
  3. How to check your site in five minutes
  4. Don't fall for fake "WordPress security update" emails
  5. How Padideban helps on your Windows PC
  6. Frequently asked questions
  7. Sources

If you run a WordPress site, update it to WordPress 7.1.4 (or the latest security release for your branch) today. On November 3, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added a WordPress core flaw, CVE-2026-119977, to its list of vulnerabilities that attackers are already using. The fix has been available since October 28, so most sites only need a quick check that the update actually happened.

This guide explains what the WordPress 7.1.4 security update fixes, who is at risk, and how to confirm your site is safe in about five minutes.

What happened

WordPress released version 7.1.4 on October 28, 2026 as a security release. It fixes several security issues. The most serious one is a weakness in the update process itself, which could let an attacker run code on the server during the short window while WordPress upgrades.

Six days later, CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities (KEV) catalog. KEV is a public list of flaws with evidence of real attacks, not just theoretical risk. According to the catalog entry, the bug is a "time-of-check time-of-use" race condition. In plain words: during a full core upgrade, WordPress used temporary files in predictable, web-reachable places, and an attacker who timed a request right could slip in their own code. No login is needed.

U.S. federal agencies have until November 6 to fix it. Everyone else should treat that date as a strong hint.

Who is at risk

  • Self-hosted WordPress sites (WordPress.org software on your own hosting) that are still on a version older than the fixed release for their branch.
  • Sites where automatic updates are turned off, or where a host or plugin blocks them.
  • Older sites on branches back to 4.7. WordPress says it backported the fixes to all branches that still get security fixes, but it also notes that only the newest version is actively supported.

If your site is hosted on WordPress.com or a managed WordPress host, core updates are usually handled for you. It's still worth checking the version number.

How to check your site in five minutes

  1. Log in to your dashboard yourself. Type your site's address in the browser. Don't use links from emails that claim to be "urgent WordPress update" notices (see below).
  2. Go to Dashboard → Updates. The page shows your current version. If it says WordPress 7.1.4 or newer, the core fix is in place.
  3. If an update is offered, back up first, then click "Update Now." Most hosts have a one-click backup. A backup takes a minute and makes any update easy to undo.
  4. Update plugins and themes too. The core fix doesn't cover them, and outdated plugins are a common way in.
  5. Turn on automatic updates for minor and security releases. WordPress says sites with background updates enabled start updating automatically. On the Updates page you can confirm this setting.
  6. Look for anything you didn't create. Check Users for unknown administrator accounts, and ask your host whether they see unfamiliar PHP files in your WordPress folders. If something looks wrong, ask your host for help before you change anything else.

Don't fall for fake "WordPress security update" emails

News about a real bug is often followed by fake alerts. Criminals send emails that look like they come from WordPress or your host, saying you must "install a security patch" from a link or attachment. The link usually leads to a fake login page or a plugin file with a backdoor.

A simple rule protects you: WordPress updates come from inside your dashboard, not from email attachments. If an email asks you to download a plugin or a patch, ignore it and check the Updates page yourself.

How Padideban helps on your Windows PC

Padideban protects the Windows computer you use to manage your site, not the web server. That still matters, because a stolen admin password from your PC can be as bad as a server bug. The free Banking Anti-Phishing feature checks links and flags look-alike login pages, and the free Download Inspector checks files you download before they run, which helps against fake "security patch" files. The free Security checkup also points out weak Windows settings.

No tool can update your website for you, so the steps above come first. You can read how the link checker works in our anti-phishing guide or download Padideban for free.

Frequently asked questions

Is my site hacked if it wasn't updated yet?

Not necessarily. Being on an old version means your site could be attacked, not that it was. Update now, then check for unknown admin users and strange files. If you find any, ask your host for a malware scan.

Does WordPress update itself automatically?

Often, yes. WordPress says sites that support automatic background updates will receive 7.1.4 automatically. But hosts, plugins and settings can turn this off, so always confirm the version on Dashboard → Updates.

Do I need 7.1.4 exactly if I'm on an older branch?

WordPress backported the fixes to every branch that still receives security fixes. If you can't move to 7.1.x yet, update to the latest release of your branch. Moving to the newest version is the safest choice, because only it is actively supported.

What is the CISA KEV catalog, and why should I care?

It's a public list of security flaws that attackers are known to be using. When a bug lands on it, the risk is no longer theoretical. It's a good signal to patch quickly, even if you're not in the U.S.

Sources

Share: Telegram WhatsApp X LinkedIn

Read more