BuddyForms ≤ 2.10.5: A Logged-Out Visitor Can Plant a Form That Mints Administrators (CVE-2026-107622, CVSS 9.8)

Running BuddyForms on your site? Check it against CVE-2026-107622 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your BuddyForms is in the affected range (≤ 2.10.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 →

BuddyForms ≤ 2.10.5: A Logged-Out Visitor Can Plant a Form That Mints Administrators (CVE-2026-107622, CVSS 9.8)

A form builder's submission handler trusts two things from the same request: "this form allows public submissions" and "make the new object a form definition." In BuddyForms — the WordPress form-builder plugin by Themekraft — versions up to and including 2.10.5 never check that those two claims belong together, and the gap between them is an administrator account. That is CVE-2026-107622, scoring CVSS 9.8, disclosed November 6, 2026 (CNA: Wordfence).

What Happened

CVE-2026-107622 is an unauthenticated privilege escalation vulnerability (CWE-269, improper privilege management) in the BuddyForms plugin (wordpress.org slug buddyforms, 800+ active installs on the free listing at disclosure time; the plugin also ships in premium bundles the directory does not count).

Am I Affected?

Check wp-admin → Plugins for BuddyForms and its version. At 2.10.5 or below, with open registration and a public form, your site runs the affected code in the plugin that handles its form submissions — which, for this plugin, is also its account-creation machinery.

Our scanner checks it: run the free mini-scan, or check just this plugin at /tools/plugin-check?slug=buddyforms. The check reads the version your site announces and flags 2.10.5 and below. A version above 2.10.5 earns no "patched" claim from us, though — the CVE record names no fixed version, so the check stays silent above the affected range rather than calling any release the fix. A version read also proves neither of the record's deployment conditions — only that the site runs an affected version.

What To Do Now

  1. Update BuddyForms to the newest available release today. The CVE record names no fixed version, so do not treat any specific release number — from us or anyone else — as a verified "fixed in" claim for this CVE.
  2. Audit Users → All Users for administrators you cannot name, and review the form list for definitions you did not create. The rogue form and the rogue account are both artifacts you can look for directly.
  3. If the site does not need open registration, turn "Anyone can register" off. The CVE record names it as one of the two deployment conditions this chain needs — removing it closes the stated exploitation path.

The Bigger Lesson

Form builders are account-creation machinery wearing a design tool's clothes. Any plugin that can register users is identity infrastructure, and it inherits identity-grade rules: the decision "may this request create an object?" and the decision "what type of object may it create?" must come from the same authorization, checked server-side, every time. BuddyForms checked the first from the form's own flag and took the second from the request — and everything after that was bookkeeping.

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 user or form audit finds something you do not recognize.


Running WordPress with BuddyForms? Update to the newest release today, audit your administrators and your form list, then run the free check at preshipit.com/free-scan — our scanner checks it, version-checking this plugin against CVE-2026-107622 from the version your site announces to the world.

Check BuddyForms on your own site — free.

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

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your BuddyForms is in the affected range (≤ 2.10.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