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 →The most dangerous seconds in a WordPress site's life are the ones when it is updating itself. WordPress 7.1.4, released October 28, 2026, patches a race condition in the Core update process that can give an unauthenticated attacker remote code execution — and according to Wordfence, attackers spent the first day after the release polling sites for exactly those seconds: more than 18,500 requests targeting staged installer paths in the first 21 hours, starting nine minutes after Wordfence deployed its firewall rule.
WordPress 7.1.4 is a security release fixing 22 vulnerabilities. The most serious is a race condition in the Core upgrade process, reported by Umut Bayram: during a full-package Core update, WordPress unpacks the new files into a staging directory beneath wp-content/upgrade. That temporary copy is a complete WordPress — installer included — and on many servers it is web-accessible. An attacker who requests the staged installer (wp-admin/setup-config.php) at precisely the right moment can interact with the staged copy and progress to executing PHP code on the server. No account, no login — just timing.
Both of these things are true, and any write-up that gives you only one of them is selling something:
The practical conclusion isn't panic; it's ordering. You cannot control when an attacker polls. You can control whether, the next time your site updates itself, it is already running the fixed code.
If your site runs WordPress 4.7 through 7.1.3 — or an older branch's pre-patch release (6.8.11 and below, 6.0.17 and below, all the way back to 4.7.38) — it was in the affected range when 7.1.4 shipped. Most sites receive security releases like this through automatic background updates, so by now many have silently patched themselves. Verify, don't assume: Dashboard → Updates shows your current version. Our free mini-scan now classifies the Core version your site discloses publicly against the per-branch patched table and flags an affected one — with the race-window scope stated, because that's the honest claim the version alone supports.
wp-content/upgrade, and audit administrator accounts and installed plugins for anything you don't recognize. Wordfence has reported exploitation attempts, not confirmed compromises — this is a hygiene pass, not an incident declaration.Every site owner's mental model of patching is "old version bad, update good." This flaw inverts the middle of that sentence: the act of updating was the exposure, because the updater staged a runnable copy of the application in a public directory under a predictable name. Updaters, installers, importers, and migration tools are attack surface — they run with total trust, often before authentication exists, and they are exactly the code paths a fast-shipped site never reviews. It's the same shape as the Prime Mover object injection: a routine maintenance action — there an export, here an upgrade — is what turns stored or staged material into code execution.
Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the log review finds something you can't explain.
Running WordPress? Run the free check at preshipit.com/free-scan — it reads the Core version your site announces and flags the upgrade-window RCE range, race-window scope and all.
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