The update that fixes this WordPress flaw is also the moment it can be used. On November 3, CISA confirmed attackers are using the WordPress update flaw, and it sits in every version of WordPress from 4.7 through 7.1.3.
Here is what happened, day by day, how the flaw works, what to ask your host this week, and what a website with no update to run looks like.
What happened, day by day
On October 28, WordPress released version 7.1.4. Among its fixes was "a weakness in the upgrade process which can lead to remote code execution during the upgrade window." WordPress told every site owner to update immediately.
The flaw was found by Umut Bayram, a researcher at Picus Security. WordPress sent the fix back to every older version it still patches, down to 4.7, and sites with automatic updates on began updating themselves.
Attackers moved within days. Wordfence, a WordPress security company, said it blocked 13,095 attacks on this flaw in a single 24 hours, BleepingComputer reported.
On November 3, the US Cybersecurity and Infrastructure Security Agency added the flaw to its list of flaws attackers are using now. Canada's Cyber Centre issued its own advisory the same day for every WordPress version before 7.1.4.
Federal agencies had until November 6 to fix their sites. CISA has not named any victims, and as of this week no one has reported a site taken over through this flaw, Ostorlab wrote. What is being counted so far is attempts.
How the WordPress update flaw works
When WordPress updates itself, it unpacks a fresh copy of WordPress into a folder on your server. The folder's name is predictable, and for a few seconds the setup page inside that copy can be opened from the internet.
An attacker who reaches that page in those seconds can point it at a database they control and run their own code on your server. No login is needed.
In lab tests the window lasted seconds, so attackers keep requesting the page over and over to catch it, eSecurity Planet reported.
Once their code runs, they can add an administrator account and install a plugin of their own. From there the site is theirs.
Ostorlab adds one more detail. The update that installs 7.1.4 still runs the old update code, so the window can open one last time while the fix goes in.
The update is the fix, and the update is the window.
WordPress has been here before this year
In July, WordPress patched a different pair of flaws, known as wp2shell. Public exploits appeared a day after the patch. By September, attackers had used them to steal more than 18,500 records from small business and government databases, per BleepingComputer.
Two weeks ago, the PHP2Shell cyber attack hit PHP, the language WordPress runs on. That fix lives on the server. This one lives in WordPress itself.
Three weeks after 7.1.4, the WordPress 7.1.5 security release fixed 20 more issues.
What to ask your host this week
For most small businesses, the hosting company or a web developer runs the updates. Send them these questions in writing:
- Is the site on WordPress 7.1.4, or the fixed release for its version: 7.0.8, 6.9.11, 6.8.12 or 4.7.39?
- Is web access to the wp-content/upgrade folder blocked before the next update runs?
- Have you checked for administrator accounts, plugins or files nobody on the team added?
If they find something, eSecurity Planet's advice is to keep the logs and bring in help before deleting anything. Then change the website and hosting passwords.
A site with no update to run has no window
Freeborn Digital builds every website as plain pages: HTML, CSS and JavaScript, the three things a browser reads. There is no WordPress, no PHP, no database and no plugin on the site.
There is no copy of WordPress to unpack and no setup page waiting on the server. The flaw needs both, and a Freeborn Digital site has neither. The attempts Wordfence counted would find nothing to open.
Take a heating and cooling company in Pottsville whose WordPress site updated itself overnight. The owner learned about it from an email from the host, and spent the morning on hold asking whether the site had been touched.
On a plain-page site, the change that week is the winter hours. The owner texts them to Freeborn Digital and they go up. Freeborn Digital builds this as custom websites, launches it, and keeps it current.
Questions about the WordPress update flaw
Do automatic updates protect my WordPress site?
They install the fix, which is the main thing. Ostorlab notes the update that installs 7.1.4 still uses the old code, so the window can open during that update. Ask your host to block the upgrade folder first.
Is this the same as PHP2Shell?
No. PHP2Shell is a flaw in PHP, fixed on the server by your host. The WordPress update flaw is in WordPress itself and is fixed by updating WordPress. A WordPress site needs both fixes.
Has anyone's website been hacked through this flaw?
CISA says attackers are using it and has named no victims. As of this week, no one has reported a site taken over through it. Wordfence alone blocked 13,095 attempts in one day.
Does a Freeborn Digital website need this update?
No. A Freeborn Digital website has no WordPress on it, so there is no WordPress update to run. The pages are plain HTML, CSS and JavaScript on your own domain.
If your site runs on WordPress, send your host the three questions today, before its next update. For a site with no update window, tell Freeborn Digital what the business does. A few lines at freeborndigital.com/start is enough, or text 570-617-7655.
Want this for your business?
Start a Project