WordPress security
wp2shell needed a WordPress that answers, and a static copy doesn't.
wp2shell was a chain of two flaws in WordPress itself, fixed on 17 July 2026 in WordPress 7.0.2 and 6.9.5. Anyone on the internet could use it to run code on an unpatched site, with no account and no plugin needed, through an address every WordPress answers. A site whose visitors get a static copy never hands their requests to WordPress, so that address wasn't there to attack. The WordPress behind it still needed the update.
Your whole site, on your own domain.
Free while we're in beta. No credit card.
Test it on one of your pages
About twenty seconds, no account. You see your page and the copy side by side and click through it yourself.
A copy that works like your site
A plain HTML export saves each page with the files it links to. Anything a page loads only after it opens, like images that appear as you scroll, a menu that fills in, content a script fetches or a link that redirects, often goes missing. And you hear about it from a visitor.
A MakeStatic copy doesn't just look like your site, it works like it. You try it yourself, side by side with your site, before you decide anything. Should a page of the copy ever behave differently from yours, write to [email protected] and we'll fix it.
- Images that load as you scroll, in every size your site has for phones and big screens.
- Fonts, icons and everything your theme or page builder brings along.
- Content a script loads after the page opens, and menus that fill in on hover.
- Links that redirect to another address still redirect.
- Videos that play and let you skip ahead.
- Contact forms that deliver and a search box that answers.
What wp2shell was
It was two vulnerabilities used together, CVE-2026-63030 and CVE-2026-60137. The first lets a request slip through the batch interface of WordPress's REST API. The second turns that request into a database query the attacker writes, and in the end, code runs on the server. The researcher who found it, Adam Kues of Assetnote / Searchlight Cyber, showed it working against a plain installation with no plugins, used by an anonymous visitor.
Together the two are rated 9.8 out of 10. Germany's Federal Office for Information Security (BSI) warned of active exploitation after the first attack code appeared within hours of the fix, and the US agency CISA listed both flaws as exploited on 21 July 2026.
Which versions it hit and what fixed them
- WordPress 6.9 up to 7.0.1: both flaws. Fixed in 7.0.2 and 6.9.5.
- WordPress 6.8: only the database flaw. Fixed in 6.8.6.
- Versions before 6.8 were not affected.
- WordPress pushed the fix as a forced automatic update. Sites that don't update themselves had to be updated by hand.
Why a static copy was out of reach
The attack is a request to WordPress itself, sent to /wp-json/batch/v1 or to the same interface through any other address of the site. It works wherever WordPress answers what a visitor sends.
A static copy answers every visitor with files and passes nothing a visitor sends on to WordPress. Search runs in the visitor's browser, contact forms come to us, and an address the copy doesn't have simply isn't found. Behind the public address, there was no WordPress to send the attack to.
What it doesn't change
The WordPress you edit in is still a WordPress. It stays online at its own address, and until it was updated, wp2shell worked there like anywhere else. Update it as you would any WordPress.
What the copy changes is that your public site doesn't depend on it. Nothing from the editing installation reaches your visitors until you publish, and every publish lists the pages it changed. So you'll see a page that changed without you before your visitors do.
If your site ran an affected version
- Check which version it runs. Versions 6.8.6, 6.9.5, 7.0.2 and everything after them are fixed.
- Check the site for signs of a break-in even if it's updated now, as the BSI advises, because it may have been taken over before the fix arrived.
- If it was, clean it up first. A copy shows what the site shows, including whatever was planted in its pages.
Sources
The WordPress 7.0.2 release announcement on wordpress.org; the research note by Searchlight Cyber (wp2shell.com); the entries for CVE-2026-63030 and CVE-2026-60137 in the US National Vulnerability Database; the BSI's warning of 20 July 2026; Bitdefender's technical advisory. Checked on 28 September 2026.
Frequently asked questions
- Does wp2shell need a login?
- No. The researchers and the US National Vulnerability Database both say it needs no account of any kind. The sentence about authenticated users on wp2shell.com describes the stopgap plugin offered there, which switches off anonymous batch requests.
- My site uses no plugins. Was it affected?
- Yes, if it ran WordPress 6.8 to 7.0.1 without the fix. The flaw was in WordPress itself, not in a plugin.
- Would a firewall or a security plugin have stopped it?
- Once there was a rule for it. After the flaw became known, security vendors published rules that block anonymous requests to the batch interface. A static copy didn't need one, because it has no such interface to block.
- Is a static site safe from every attack?
- No. It has no WordPress for a visitor to reach, which takes attacks like this one off the table for your public site. The WordPress you edit in, your domain and your email accounts still need looking after.
Free while we're in beta
MakeStatic is new. While it's in beta, you get all of it for free, including your whole site on your own domain, with no credit card and no commitment.
At some point it will cost something. When there's a price, you'll see it before anything about your site changes.