ACF Extended < 0.9.2.8: Unauthenticated Post Overwrite That Can Reach Code Execution (CVE-2026-94267, CVSS 9.0)

Running ACF Extended on your site? Check it against CVE-2026-94267 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your ACF Extended is in the affected range (< 0.9.2.8), 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 →

ACF Extended < 0.9.2.8: Unauthenticated Post Overwrite That Can Reach Code Execution (CVE-2026-94267, CVSS 9.0)

Front-end forms are where a WordPress site stops being a brochure and starts trusting its visitors. CVE-2026-94267 is what happens when that trust skips a step: in ACF Extended versions before 0.9.2.8, a front-end form's post-update action can run without any capability check — so an unauthenticated visitor who finds the right form can overwrite arbitrary posts, a path that can reach code execution.

What Happened

CVE-2026-94267 affects Advanced Custom Fields: Extended and ACF Extended PRO, the widely used companion plugins that add front-end forms and richer field tooling to ACF sites. The CVE record was published October 23, 2026.

The Scope, Stated Straight

Not every ACF Extended site is exposed the same way:

That precondition is why the CVSS vector carries AC:H — and it is also why "we don't use those forms" needs to be a checked fact about your site, not a guess. ACF Extended forms accumulate quietly on long-lived sites.

What To Do Now

  1. Update to 0.9.2.8 or later — free and PRO.
  2. Audit the front-end forms you publish. Any form using the post-update action should be reviewed for where its target and content values come from.
  3. Review recently edited posts and pages for content you do not recognize, especially anything edited without a matching author session.
  4. Check the version you're announcing. ACF Extended's public readme discloses its version; our free mini-scan now flags sites below 0.9.2.8 — from the same public signal an attacker would use to find them.

Front-end editing is a legitimate, useful feature — right up until the form forgets to ask who is submitting. Patch first, then make the form audit a habit: every published form is a small admin panel you handed to the internet, and it should be reviewed like one.

Check ACF Extended on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls ACF Extended's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-94267 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 ACF Extended on your site? Check it against CVE-2026-94267 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your ACF Extended is in the affected range (< 0.9.2.8), 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