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 serious unauthenticated flaw in WordPress 7.1.5 does not break down the door. It hands the site's own editor a pre-filled create-user request and waits for an administrator to open the link. WordPress 7.1.5, released November 18, 2026, patches it — along with 18 other vulnerabilities Wordfence tracks in the release.
The lead flaw is a privilege escalation via Template Part block attributes. Wordfence Intelligence classifies it precisely: a client-side CSRF via a Template Part entity key. An unauthenticated attacker prepares a crafted site-editor link; when an Administrator opens it, the editor constructs a create-user REST request carrying the victim's own nonce and creates an attacker-chosen Administrator account.
WP_Meta_Query relation values (7.5) and an unauthenticated stored XSS via shortcode attributes in comments (7.2). The remaining items are authenticated issues and two hardening changes.If your site runs WordPress Core 5.9.0 through 7.1.4 — or an older branch's pre-patch release (6.8.12 and below, 6.0.18 and below, all the way back to 5.9.20) — it is in the affected range. Most sites receive security releases like this through automatic background updates, so 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 this flaw's own per-branch patched table and flags an affected one — with the admin-opens-the-link scope stated, because that is the honest claim the version alone supports. A site that discloses no version is reported as unverified, never as vulnerable.
wp user list --role=administrator — every name on it should be a person you know.A nonce proves a request came from a logged-in browser. It does not prove the human intended it. Any flow that turns a GET link into a privileged write — creating a user, changing a role, deleting content — is a CSRF waiting for a lure, no matter how legitimate the destination looks. It's the same shape as the WordPress 7.1.4 upgrade-window RCE: a routine, trusted mechanism — there the updater, here the editor — doing the attacker's work with the site's own credentials.
Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline.
Running WordPress? Run the free check at preshipit.com/free-scan — it reads the Core version your site announces and flags the 7.1.5 Template Part range, admin-link 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