Running aBlocks on your site? Check it against CVE-2026-110018 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your aBlocks is in the affected range (≤ 2.17.0), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.
Run the free mini-scan →Most of October's WordPress flaws needed no account at all. This one needs the easiest account there is: on a site with open registration, anyone who signs up as a Contributor can promote themselves to Editor — no password theft, no admin trickery, just a feature endpoint that trusts the caller.
CVE-2026-110018 is a privilege-escalation vulnerability in aBlocks, the Gutenberg blocks and form-builder plugin, disclosed October 24, 2026 (CNA: Wordfence).
/ablocks/v1/form-builder/registration) lets the caller influence the role they end up with, up to Editor or another non-administrator role.An Editor can't install plugins, but they can publish and edit content site-wide, upload media, and rewrite your pages — a defacement and SEO-poisoning kit, handed to anyone who asked for an account.
The plugin's public readme announces its version — our free mini-scan reads it and flags the affected range, precondition stated. In wp-admin: Plugins → Installed Plugins → aBlocks. At or below 2.17.0, run the steps below. Your exposure scales with registration: open registration + aBlocks ≤ 2.17.0 is the combination that matters most.
"Authenticated" in a headline reads as "safe-ish," and on the modern WordPress web that's often wrong: registration is a feature sites enable for comments, memberships, and forms, which makes "any registered user" very close to "anyone." This was one of eleven qualifying WordPress disclosures in a single week — and the only one whose fix starts with looking at your own user list.
Related: WordPress Hardening for AI-Built Sites — registration discipline and user enumeration, the standing version of this lesson. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds a stranger.
Letting the public register on your site? Run the free check at preshipit.com/free-scan — it reads the aBlocks version your site announces and flags the affected range.
Check aBlocks on your own site — free.
Our free WordPress Plugin Vulnerability Checker pulls aBlocks's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-110018 included. No scan, no account.
Open the free plugin checker →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.
Running aBlocks on your site? Check it against CVE-2026-110018 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your aBlocks is in the affected range (≤ 2.17.0), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. 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