Formidable Forms ≤ 6.35: Any Subscriber Can Install Arbitrary Plugins (CVE-2026-89435, CVSS 8.8)

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 →

Formidable Forms ≤ 6.35: Any Subscriber Can Install Arbitrary Plugins (CVE-2026-89435, CVSS 8.8)

A form builder is the front door of a site — it takes names, emails, payments, and uploads from strangers all day. In Formidable Forms at version 6.35 and below, the cheapest account on that site could do something no form user should ever be able to do: make the site install an arbitrary plugin. CVE-2026-89435 carries a CVSS score of 8.8.

What Happened

CVE-2026-89435 is an authenticated arbitrary plugin installation vulnerability in the Formidable Forms WordPress plugin (vendor: Strategy11), disclosed October 30, 2026 (CNA: Wordfence). The plugin sits on 300,000+ sites.

Why "Subscriber-Level" Is Not Reassurance

PR:L sounds like a locked door until you remember what a form-builder site is. Contact forms, quizzes, payment forms, membership sign-ups — these sites hand out Subscriber accounts through open registration by design. On a site like that, "any Subscriber" is functionally "anyone who fills in the registration form." And the payload here is not a defaced page or a leaked row: installing a plugin is code execution on WordPress. The attacker's plugin becomes part of your site, running with your site's privileges.

Am I Affected?

Check wp-admin → Plugins for Formidable Forms and its version. At 6.35 or below, you are in the affected range.

This one is version-checkable, and our scanner checks it: the free mini-scan reads the plugin's public readme and flags a stable tag at or below 6.35 as a High finding naming CVE-2026-89435. It reads the version only — it never calls the addons endpoint and never submits a file_url. A version above the affected range earns no "patched" claim from us, because the CVE record names no fixed version — that silence is deliberate, and it is the honest reading of the primary source.

What To Do Now

  1. Update Formidable Forms to the latest available release today — the current release (7.0 at writing), whose changelog carries the permission-check and URL-validation hardening described above.
  2. Audit the installed-plugins list and administrator accounts. The flaw's payload is a plugin you didn't choose; anything you don't recognize is a compromise indicator, not a curiosity.
  3. Reconsider open registration. If strangers don't need accounts, don't issue them. Every registered user is one plugin flaw away from being the "authenticated attacker" in the next CVE.

The Bigger Lesson

A token is not a permission. The record's quiet detail — a callback that checked a token only — is the whole story in miniature: the request looked authorized because it carried a secret, but nobody checked whether this user was allowed to do this thing. Shipped-fast sites repeat that mistake in their own code constantly, in admin actions, webhook handlers, and "internal" endpoints. Every privileged action needs a real capability check, and every URL allowlist needs to validate the whole destination, not a substring of it.

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 audit step finds a stranger's work.


Running Formidable Forms? Update to the latest release, then run the free check at preshipit.com/free-scan — it flags Formidable Forms ≤ 6.35 and the rest of your site's exposed surface in about a minute.

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