WordPress Hardening for AI-Built Sites: Beyond Plugin CVEs

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

WordPress Hardening for AI-Built Sites: Beyond Plugin CVEs

When an AI agent builds a WordPress site, it installs a theme, a page builder, a form plugin, a backup plugin — and stops. The result passes the eye test and fails the enumeration test: a stock WordPress install announces itself in a dozen ways, and the month's plugin CVEs (we covered eleven disclosures in one week) do the rest.

Plugin updates matter — our scanner checks the versions your site announces against the current CVE list — but they're one layer. These are the hardening steps that sit underneath them.

1. Decide whether xmlrpc.php earns its keep

xmlrpc.php is a legacy remote-publishing endpoint that predates the REST API. Almost nothing in a modern AI-built site needs it, but it stays enabled by default, and it's a standing target for password-guessing and pingback abuse because it accepts authentication attempts outside the normal login flow.

The step: if you don't use the WordPress mobile app, Jetpack's remote features, or a service that posts remotely, disable XML-RPC at the server or plugin level, and confirm yoursite.com/xmlrpc.php no longer answers. If something you use needs it, restrict it rather than leaving it open to the world.

2. Close the user-enumeration doors

WordPress will happily list your accounts to strangers: the REST API's users endpoint (/wp-json/wp/v2/users) returns usernames and author slugs, and author archive URLs (/?author=1) redirect to the same information. Usernames are half of every login — handing them out turns credential attacks into a password-only problem.

The step: restrict the users endpoint for unauthenticated visitors, block author-ID enumeration redirects, and make sure no account uses the username "admin." While you're there, check your user list for accounts you don't recognize — after the aBlocks privilege escalation (any self-registered Contributor could promote themselves), a role audit is part of hardening, not paranoia.

3. Treat version disclosure as attack surface

Your site announces its WordPress version in the generator meta tag, and every plugin's readme.txt announces its version to anyone who asks — including, this month, versions with critical CVEs attached. That's not a flaw you can fully eliminate (a determined checker has other fingerprints), and obscurity is not a defense on its own. But there's no reason to make enumeration free.

The step: remove the generator tag, block web access to readme.html and plugin readme files where your host allows it, and — the part that actually protects you — keep versions current so the disclosure announces "patched." Our free mini-scan reads exactly these public version disclosures, the same ones attackers enumerate, and flags the ones with known CVEs.

4. Harden the login and the editor

5. The update habit is the hardening

Every item above is a one-time setting; this one is a practice. Core, themes, and plugins on automatic updates where you can tolerate it, a weekly glance where you can't, and a backup you have actually restored once — the Duplicator flaw showed why backup tooling itself belongs on the patch list, and why you don't run a migration on an unpatched version.

Related: How to Check If Your Web App Is Hacked — the signs to look for if hardening comes after the fact. Prime Mover Object Injection — the other backup-plugin lesson from October. How to Check Your Site's Security Headers — the header layer, which stock WordPress also leaves to you.


Not sure what your site is announcing? Run the free mini-scan at preshipit.com/free-scan — it reads the same public disclosures attackers do, checks them against the current WordPress CVE list, and scores the basics in about a minute.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report