Running Kirki on your site? Check it against CVE-2026-75891 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Kirki is in the affected range (≤ 6.2.5), 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 →The attacker doesn't break in — they sign up. CVE-2026-75891 needs only the lowest-privilege account on your site: a Subscriber. From there, a missing capability check in the Kirki page-builder plugin lets them inject a PHP object, and under the right conditions walk away with a reset administrator password.
CVE-2026-75891 is a PHP object injection vulnerability (CWE-502, deserialization of untrusted data) in Kirki, the freeform page builder and customizer plugin by themeum, disclosed October 27, 2026 (CNA: Wordfence).
PR:L. The attacker needs a low-privilege account first.kirki_post_apis() AJAX dispatcher deserializes untrusted input in its get-single-symbol branch with no capability check — a helper that looks like it just fetches icons takes serialized data from any logged-in user and unserializes it.The plugin's public readme announces its version — our free mini-scan reads it and flags the affected range, preconditions stated. In wp-admin: Plugins → Installed Plugins → Kirki. At or below 6.2.5, the question that decides your real exposure is whether your site lets the public register. Open registration + Kirki ≤ 6.2.5 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 logged-in user" very close to "anyone." Capability checks belong on every AJAX branch — including the ones that look like harmless icon helpers. It's the same shape as the aBlocks privilege escalation disclosed three days earlier: the trust boundary failed at the cheapest account on the site.
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 account audit finds a stranger.
Running Kirki? Run the free check at preshipit.com/free-scan — it reads the Kirki version your site announces and flags the affected range.
Check Kirki on your own site — free.
Our free WordPress Plugin Vulnerability Checker pulls Kirki's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-75891 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 Kirki on your site? Check it against CVE-2026-75891 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Kirki is in the affected range (≤ 6.2.5), 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