What happened?
WordPress has a built-in tool that updates the software for you. A researcher at Picus Security, Umut Bayram, found that during an update, WordPress briefly unpacks a copy of its own installer into a folder that can be reached from the web. An attacker who finds that copy at the right moment can run their own code on the server, add an administrator account, and take the site over. No login is needed.
The behavior goes back to WordPress 2.7, released in 2008, so it sat there for about 18 years. The timeline, as reported by The Hacker News and Hackread on November 6, 2026:
- October 28: WordPress released version 7.1.4 with the fix, and patched older versions back to 4.7.
- Same day: the security firm Wordfence reported attack attempts nine minutes after it turned on a firewall rule for the flaw.
- November 3: CISA added it to its list of flaws known to be exploited, and gave federal agencies until November 6 to deal with it.
Two things keep this in proportion. The attack only works while a site is in the middle of an update, so the attacker has to get the timing right. And nobody has published how many sites were actually broken into. The official record scores the flaw 8.1 out of 10, while WordPress’s own advisory rates it low.
Why is the fix awkward?
Because the update that installs the fix is run by the old, flawed updater. So a site is exposed one last time while it updates to the safe version. Automatic background updates take the same path. As Bayram put it, quoted by Hackread: “Until then, there’s a window where you’re exposed, and that’s exactly where attackers are working.”
What should I do if my site runs WordPress?
Send this list to whoever manages your site. If nobody does, that is the real finding.
- Check the version. It should be 7.1.4, or the patched release for an older version. WordPress 4.6 and earlier no longer get security fixes at all.
- Block the update folder first. The researcher’s advice is to block web access to
wp-content/upgrade/before updating, and confirm it returns an error page instead of files. - Then update.
- Look for anything that should not be there. Admin accounts you do not recognize, plugins you did not install, or stray files in that upgrade folder.
If your site is on a managed platform that handles WordPress for you, ask them to confirm it is done. Not sure what your site runs on? Our PHP2Shell post has a one-minute way to check.
Is this a one-off?
No, and that is the part worth sitting with. It is the second urgent fix in a month and at least the third scare this year:
| When | What | Where the flaw was |
|---|---|---|
| January 13 | Attackers logging in as admin through the Modular DS plugin, used on 40,000+ sites | A plugin |
| October 21 | PHP2Shell: emergency fixes for two critical flaws | PHP, the language WordPress runs on |
| October 28 | The updater flaw in this post | WordPress itself |
Three different layers, one result each time: someone has to notice, patch fast, and check for damage. WordPress is not badly made. It is maintained by serious people and most updated sites are fine. But it is software that has to be kept up, and most small business sites have nobody doing that.
Why doesn’t a plain HTML site have this problem?
A static site is a set of finished files. When someone visits, the server hands over the file. Nothing runs.
| Part | WordPress site | Static HTML site |
|---|---|---|
| Admin login page | Yes | None |
| Database on the site | Yes | None |
| Plugins | Usually several | None |
| Code running on every visit | Yes (PHP) | None |
| Self-updater | Yes | None |
| Security patches you must apply | Ongoing | None for the site itself |
All three emergencies above went after something in the middle column. A static site has an empty column there. This is how every Atlas Genesis site is built, and it is the main reason we build them that way.
What does a static site not protect you from?
Plenty, and anyone who tells you otherwise is selling something.
- Your form data still goes somewhere. A quote request has to land in an inbox or a system. On our sites it is sent to a separate service, not stored on the website, so a problem with the site cannot expose it. But that service has to be secure too.
- Your accounts. If someone gets into your domain account or your email, they can redirect your site or read your leads. A strong password and two-step login on those two accounts matters more than anything about how the site is built.
- Outages. A static site still lives on a host. If the host goes down, so does the site. We wrote about last week’s run of outages separately.
- Anything you add to it. A booking widget, a chat tool or an ad pixel is someone else’s code on your page.
The honest claim is narrow and still worth a lot: the website itself has no login to break into and no data sitting on it to steal.
Do I need to rebuild my site?
Not necessarily. If your WordPress site is patched and someone is watching it, you are in reasonable shape. If nobody has logged in to it in a year, that is the site these attacks find. For a brochure-style site with a handful of pages and a contact form, moving to static HTML removes the upkeep for good. We do that as a one-time switch, covered in the PHP2Shell post. If you run a store, a membership area or anything with customer logins, you likely need a platform like WordPress, and the answer is proper maintenance, not a rebuild.
Sources
- The Hacker News, Installing the fix for an exploited WordPress flaw can expose some sites one last time (November 6, 2026)
- Hackread, CISA warns hackers are exploiting 18-year-old WordPress core vulnerability (November 6, 2026)
- TechRadar, Hackers exploit WordPress plugin security flaw exposing 40,000 websites (January 16, 2026)


