A WordPress core flaw is being exploited. What should a small business do?
A flaw in WordPress's upgrade process is being used by attackers. Here is how to check your site, what auto-updates did, and when it makes sense to move.
Update your WordPress site to the latest release today, confirm the version number afterward, and then spend ten minutes looking for signs that anyone got in. That is the whole job for most small businesses, and if your site applies updates automatically, the first part has very likely happened already.
The flaw behind the headlines is tracked as CVE-2026-119977. On November 3, 2026, the US Cybersecurity and Infrastructure Security Agency added it to its catalog of vulnerabilities known to be exploited, which means attackers are using it against real sites, not just discussing it. The fix shipped a week earlier, on October 28, in WordPress 7.1.4. This article walks through what the flaw is, how to tell whether you are covered, what to do if you suspect a break-in, and how to think calmly about whether WordPress is still the right home for your website.
What actually happened?
Quick answer: WordPress fixed a weakness in the way it upgrades itself, attackers began using that weakness within days, and the US government's cybersecurity agency confirmed it. The fix is already out.
According to The Hacker News, the problem is a timing flaw, the kind security people call a race condition or "time-of-check, time-of-use". During a full update of WordPress itself, the software briefly places files in staging locations that are predictable and reachable from the web. An attacker who requests the right address during that short window can run their own code on the server. No account on the site is needed. The vulnerability is rated CVSS 8.1, which sits in the high-severity band.
The timing requirement matters. An attacker cannot simply walk in at any moment; they have to catch a site in the middle of an upgrade. In practice that means sending the same probe to a great many sites, in the hope of landing on one that happens to be updating. The Hacker News reported that Wordfence, a WordPress security company, counted more than 18,500 requests aimed at staged setup-config.php installer paths in the first 21 hours after the flaw became public.
CISA gave US federal civilian agencies until November 6, 2026 to apply the fix. That deadline does not apply to a private business, but it is a useful signal of how seriously the agency rates the threat.
The same release also closed other problems. The WordPress 7.1.4 announcement lists 13 items: 12 security fixes, most of them stored cross-site scripting issues in editor content and the Interactivity API, plus an update to the bundled root certificates. The WordPress team says it backported the fixes to every branch still eligible for security fixes, currently as far back as version 4.7.
Is my site affected?
Quick answer: If your site runs WordPress and has not yet installed 7.1.4 (or the matching security release for its older branch), it was exposed to this flaw. Once the fixed release is installed, this particular weakness is closed.
There is no need to guess. You are affected if all of the following are true:
- your website runs on WordPress, not a hosted builder or a different system;
- it has not been updated since October 28, 2026;
- it could perform a full core update while someone was probing it.
The version number is what settles it. If you are on the 7.1 line, you want 7.1.4 or later. If your site sits on an older line that still receives security fixes, you want the newest release on that line, published the same day. If you are not sure what any of this means for your site, ask whoever hosts or maintains it a single direct question: "Are we on a release that includes the October 28 security fixes?" A good host can answer that in minutes.
Plugins and themes are a separate question. This flaw lives in WordPress core, the main software, so a plugin update does not fix it and a plugin vulnerability does not cause it. Your plugins still need their own updates, on their own schedule.
Did automatic updates protect me?
Quick answer: Probably, yes. WordPress says sites with automatic background updates enabled receive this release on their own, so most sites got it without anyone lifting a finger.
The WordPress project rolls out security releases through its background update system, and the 7.1.4 announcement states plainly that sites supporting automatic background updates update automatically. Unless someone switched that behavior off, your site has most likely already updated itself.
Three situations break that assumption, and they are worth checking:
- Updates were turned off on purpose. Some developers disable automatic updates to stop a plugin conflict from breaking a site unexpectedly. If that happened years ago and nobody remembers, the site may have been sitting still ever since.
- The host manages updates instead. Many managed WordPress hosts control the update schedule themselves. Most are prompt with security releases, but it is worth confirming the date.
- The update failed quietly. File permission problems or a full disk can stop an automatic update without any obvious sign on the front of the site.
One more point deserves a moment. The flaw is triggered during an upgrade, so the update itself is the moment of exposure. That sounds alarming, but it is a reason to update promptly, not a reason to wait: the 7.1.4 release fixes the upgrade process, and a site that stays on an older version keeps the weakness for every future update.
How do I check which WordPress version I'm running?
Quick answer: Log in to your WordPress admin and open Dashboard → Updates. The page tells you the version you have and whether a newer one is waiting.
Here is the short routine:
- Log in at your site's admin address.
- In the left menu, go to Dashboard, then Updates.
- Read the line near the top. It says either that you have the latest version or that an update is available.
- If an update is available, take a backup (most hosts offer a one-click backup), then click Update Now.
- When it finishes, return to the same page and confirm it now reports the current release.
If you cannot log in, or your login does not show an Updates page, you are probably not an administrator on the site. That is fine; ask the person who is. Note their answer and the date somewhere you will find it again, because the next security release will raise the same question.
For anyone who wants a second check, Tools → Site Health in the WordPress admin also reports the version and flags whether background updates are working. A warning there about automatic updates is worth passing to your host.
What should I do if I think my site was hacked?
Quick answer: Do not wipe anything yet. Contact your host, preserve a copy of the site as it is, change every password connected to it, and restore from a backup taken before the problem began.
The signs are not always dramatic. Look for:
- administrator accounts you did not create, under Users in the admin;
- pages that redirect visitors elsewhere, especially only on phones or only from search results;
- strange new pages in search results under your domain, often in another language or selling something;
- a warning from your host, your browser or Google Search Console;
- files in your hosting account with recent dates that nobody on your team changed.
If any of those appear, work through these steps in order:
- Call or ticket your host first. They can see server logs you cannot, and many will help clean a site or restore it.
- Keep a copy of the compromised site. It feels wrong, but a snapshot helps work out what was taken and when, which matters if you hold customer information.
- Change passwords everywhere. Every WordPress administrator, the hosting account, the database, any FTP or SFTP login, and the email account that receives password resets.
- Restore from a clean backup dated before the first sign of trouble, then immediately update WordPress, every plugin and every theme.
- Remove accounts you do not recognize and review who still needs administrator access at all.
- Watch the site for a few weeks. Attackers sometimes leave a second way back in.
If your site collects anything sensitive, such as patient details, financial information or payment data, also speak with your compliance person or legal counsel early. Depending on your industry and location, a break-in can carry notification duties, and they are the right people to tell you what applies.
Which businesses should be most concerned?
Quick answer: Any business whose website handles regulated information or money should treat this as a priority today: healthcare practices, financial firms, nonprofits taking donations online, real estate offices with lead forms, and any shop with a checkout.
The flaw is the same for everyone, but the consequences are not. A bakery whose site is defaced for a morning has a bad day. A practice whose appointment form is quietly copied has a much harder conversation.
- Healthcare. Contact and booking forms can carry health details. Our healthcare industry page covers how practices approach their websites more broadly.
- Financial services. Advisors and accountants often have client portals, document upload links or forms asking about someone's finances. See the financial industry page.
- Nonprofits. A donation page is a payment flow, and donor lists are valuable to attackers. The nonprofit page has more.
- Real estate. Lead forms gather names, phone numbers, addresses and buying intentions, and a compromised listing page can redirect buyers elsewhere. See real estate.
- Any shop with a checkout. Code running on a checkout page can watch what customers type.



The three pictures above are Loam's example websites for invented businesses, built so we can show our work without showing a client's. The practice, the advisors and the agency are fictional; the websites are real and working. You can see all ten, in light and dark mode, in our custom website examples, or browse by field on our industries page.
Is WordPress still safe to use?
Quick answer: Yes, when it is kept up to date and looked after by someone who checks it regularly. The risk is less about WordPress itself and more about how many moving parts a typical site has and whether anyone watches them.
It would be unfair to read this episode as proof that WordPress is careless. The project found the problem, fixed it, backported the fix across many older versions and pushed it out automatically. Its security team has also been unusually busy: in an update on the Core Security Initiative, it reported shipping four security releases in 41 days, with 7.1.1 on September 17, 7.1.2 on September 22, 7.1.3 on October 6 and 7.1.4 on October 28. That pace reflects a team putting a lot of effort into finding and closing problems.
For a small business owner, though, the practical question is different: who on your side notices each of those releases and confirms your site took it? Core is only one layer. Most WordPress sites also run a theme and a collection of plugins from different authors, each with its own update cycle, and each one is another place where a fix can be missed. A site that is cared for every month is in a very different position from one that was built five years ago and left alone.
Should I leave WordPress?
Quick answer: Not because of one flaw. Consider moving if keeping the site patched has become a burden nobody owns, if the site is old and fragile, or if it handles sensitive information and you want fewer things to maintain.
Plenty of businesses are well served by WordPress, particularly those with a developer or host who keeps everything current. Leaving is a reasonable choice in a few specific situations:
- nobody on your team or your host is clearly responsible for updates;
- the site depends on plugins that are no longer maintained by their authors;
- every update is nerve-racking because something usually breaks;
- you handle patient, client or donor information and want the smallest practical surface to look after;
- the site needs a redesign anyway, so the cost of moving is mostly already planned.
If none of those describe you, the better move is usually to tighten the care around your current site: confirm automatic updates are on, get a backup schedule in writing and decide who checks the site each month.
What does a migration involve, and what do I keep?
Quick answer: A careful migration keeps your content, your page addresses and the search standing you have built, and it moves your team to an editor they can manage. Done well, visitors and search engines barely notice anything but the improvement.
Business owners worry most about losing three things, so here is how each is handled:
- Your content. Pages, articles, team bios, service descriptions and images are carried across, then checked page by page so nothing is quietly dropped.
- Your addresses. Every page's web address is either kept exactly as it was or pointed to its new home with a permanent redirect, so old links, bookmarks and printed materials keep working.
- Your search standing. Keeping addresses, page titles and descriptions intact, and submitting a fresh sitemap after launch, gives search engines everything they need to carry your existing position forward. Nobody honest can promise rankings, but a migration should never be the reason you lose them.
The usual order is an inventory of every page, a design for the new site, the content move, a review on a private preview address, and then the switch. Your current site stays live until the new one is approved. If you would like to see how we approach it, our WordPress migration page sets out the process in full, and our websites service describes what we build.
What does a Loam website do differently?
Quick answer: It removes some of the work rather than promising to be unbreakable. There is no plugin marketplace to keep patched, and a person reviews security and dependencies every month and sends you the report.
No website can honestly be called impossible to hack, and we would not trust anyone who said otherwise. What we can describe is how a Loam site is put together, the same way our example sites describe it:
- No plugin marketplace. Features are built in and maintained together, so there is no stack of third-party add-ons with separate update schedules.
- No public data API. Someone who is not logged in can read the pages but cannot pull down the content behind them.
- No secrets in the page. Integration keys stay on the server.
- No default passwords. Admin accounts are never created with a known password.
- Forms protected against spam, with a hidden honeypot, a same-site check and a per-visitor rate limit.
- A monthly review by a person, covering security and dependencies, with a plain-language report of what was done.
You also own the important pieces: your domain is registered in your name and your content lives in a database account you control, so it goes with you if you ever move on.
If this week's news has you wondering whether your current setup is the right one, we are happy to talk it through, including telling you when staying put is the better answer. Get in touch here.
Post Details
November 9, 2026