WordPress sites got two urgent security fixes in a month. What a plain HTML site avoids

On November 3, 2026, the US cybersecurity agency said attackers were exploiting a flaw that has been in WordPress since 2008. It came two weeks after the PHP emergency. Here is what happened, what to do, and where a simple site is safer and where it is not.

A laptop showing a website admin login screen on a truck tailgate at a job site, with a padlock on the keyboard

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:

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.

  1. 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.
  2. 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.
  3. Then update.
  4. 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:

WordPress-related emergencies in 2026
WhenWhatWhere the flaw was
January 13Attackers logging in as admin through the Modular DS plugin, used on 40,000+ sitesA plugin
October 21PHP2Shell: emergency fixes for two critical flawsPHP, the language WordPress runs on
October 28The updater flaw in this postWordPress 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.

What an attacker can aim at
PartWordPress siteStatic HTML site
Admin login pageYesNone
Database on the siteYesNone
PluginsUsually severalNone
Code running on every visitYes (PHP)None
Self-updaterYesNone
Security patches you must applyOngoingNone 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.

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

Find out what your site runs on.

The free audit reads your site and tells you what it is built on, how fast it is, and what is holding it back in search. No call needed.

Run the free audit
Atlas is built for your trade
Roofing → HVAC → Plumbing → Electrical → Paving → Landscaping → Pool → Windows & Doors → Painting → Concrete → Pressure Washing → Junk Removal → Excavation → Fencing → Decks → Garage Doors → Tree Service → Restoration →

Not sure what you need?

Leave your number. We'll call you.

No sign-up and nothing to figure out. Tell us who you are and Ryan will call you back to talk it through. You don't need to know what Genesis or Orion is.

What can we help with? (optional, pick any)

We'll only use your number to call or text you about this. Prefer to call us? (732) 978-1826

Got it. Thanks.

Ryan will reach out soon at the number you gave us.

Link copied to clipboard