Services

Start a project Chat on WhatsApp
News & Insights

WordPress Owners, Check Your Version Tonight: CISA Lists a Core Flaw as Exploited

If your business website runs on WordPress, tonight is a good night to check one number: your WordPress version. The United States Cybersecurity and Infrastructure Security Agency, known as CISA, has added a WordPress core flaw to its list of vulnerabilities with evidence of active exploitation. That listing is the clearest signal a small business owner will get that an update should not wait for a quieter week.

What happened

On 28 October 2026, WordPress released version 7.1.4 as a security release fixing 22 vulnerabilities. One of them was a flaw in the core upgrade process. During a full package core update, WordPress unpacks the new files into a staging folder. In the affected versions, that folder path could be predicted, and an attacker who reached the staged installer during that short window could run code on the server. Because the attacker needs no account on the site, and only needs to win a race against the update finishing, researchers describe it as an unauthenticated upgrade window flaw.

Wordfence, which assigned the flaw the identifier CVE-2026-119977, published its record on 31 October 2026 and scored it 8.1, which it rates as High. The flaw affects WordPress Core versions 4.7 through 7.1.3. The fix is in WordPress 7.1.4, with the same fix backported to older branches, including 7.0.8 and 6.9.11.

On 3 November 2026, CISA added CVE-2026-119977 to its Known Exploited Vulnerabilities catalog, which means CISA has evidence of active exploitation. CISA set 6 November 2026 as the remediation date for United States federal civilian agencies.

Three honest limits belong with that headline. First, the 6 November date is a deadline for those federal agencies, not a deadline imposed on small businesses. It still matters for everyone else, because it shows how seriously CISA treats the flaw. Second, WordPress itself rates this issue Low in its own advisory, while Wordfence scores it 8.1 High. Both can be true at once: the attack window is short and hard to win, but the result if it is won is serious. Third, the evidence reported so far is about exploitation attempts being blocked, with Wordfence reporting tens of thousands of blocked attempts in a day. The sources checked for this post report no confirmed successful compromise. A blocked attempt is a warning, not proof that a site has been broken into, and it is also not a reason to ignore the warning.

What it means for a small business

For most small business owners, the message is simpler than the technical detail. If your site updates itself automatically, it has probably already moved to a fixed version, and a quick version check will confirm that. If your site is updated by hand, or if it is running an older version because an update was put off, the risk is that the next update, or an update left half done, opens the very window attackers are probing.

A hacked business website is not only a technical problem. It can show visitors the wrong content, damage trust built over months, and take the site offline while it is cleaned up. The cost of that disruption is almost always larger than the few minutes an update takes. This is also a useful reminder that a website is not finished on launch day. Keeping the core, themes, and plugins up to date is part of owning the site, in the same way that locking a shop at night is part of running it.

What to do about it

First, check your version. In your WordPress dashboard, look at the Updates screen, or ask whoever looks after your site to confirm the version for you. If you are on 7.1.4, or on a backported fix for your branch such as 7.0.8 or 6.9.11, you have the fix for this flaw.

Second, take a backup before you update, if you do not already have a recent one. Use your hosting backup or a backup plugin you trust. An update should be routine, but a backup turns a bad surprise into a short restore.

Third, update WordPress core to a fixed version, then update your themes and plugins. Update in that order, and check the site afterwards, starting with the homepage, the contact page, and any booking or order page. If anything looks wrong, restore the backup and ask your developer for help rather than pressing on.

Fourth, if you cannot update right away, ask your hosting provider or developer about blocking web access to the upgrade folder until the update is done. That is a temporary measure, not a substitute for updating, and it should come from someone who knows your setup.

Fifth, after updating, do a quick look around for anything unfamiliar: admin users you do not recognise, posts or pages you did not create, and files that do not belong. If you find anything strange, do not try to clean it quietly on your own. Get help from your developer or host, and keep a copy of any logs they ask for.

Finally, switch on automatic updates for minor and security releases if your site supports them, so the next security fix does not depend on someone remembering to check. Major updates can still be planned, but security fixes should not wait.

What not to do

Do not ignore the update because your site looks fine today. A site can look normal while an old version sits unpatched, and the probing reported this week is aimed at exactly that kind of site. Do not update without a backup, and do not install an update or a security plugin from an unfamiliar source promising to fix this flaw for you. Use the update inside WordPress itself, or your hosting control panel, and nothing else.

Digilistan builds and maintains WordPress websites for small businesses, and this story is a reminder of why that maintenance matters. A website that is kept up to date, backed up, and checked after every update is a website a customer can trust. Check your version tonight, update if you need to, and that trust stays intact.

Source note: Sources: WordPress 7.1.4 security release, 28 October 2026; WordPress advisory GHSA-4w3m-c66w-69mg; Wordfence CVE record for CVE-2026-119977, published 31 October 2026, CVSS 8.1 High, affected versions 4.7 through 7.1.3, fixed in 7.1.4 with backports including 7.0.8 and 6.9.11; CISA alert and Known Exploited Vulnerabilities catalog entry, 3 November 2026, with a 6 November 2026 remediation date for United States federal civilian agencies. The statement that sources report blocked attempts and no confirmed successful compromise reflects the reports checked for this post, including Wordfence and the 4 November 2026 coverage of the CISA listing.

Start the conversation

Tell us what you are building

Whether you need a website, a chatbot that never sleeps or a workflow that gives your team its evenings back, start with a short conversation. We reply to every serious enquiry personally.

  • Your message goes to the founder, not a call center.
  • We suggest the smallest service that fixes the problem.
  • The first conversation costs nothing but a few minutes.

Prefer to talk first? Message us on WhatsApp and skip the form.

Chat with us