Skip to main content
← Vulnerabilities

BuddyForms <= 2.10.5 - Unauthenticated Privilege Escalation to Form-Type Confusion via 'bf_post_type' Parameter

BuddyForms versions up to and including 2.10.5 are affected. The fix is in 2.10.6.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

9.8CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 2.10.6
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.10.6.

Published
Last modified
30/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

The BuddyForms WordPress plugin has a privilege escalation flaw that lets a remote attacker create a new account with administrator privileges, giving them full control of the site. The attacker reaches it over the network by submitting a public BuddyForms form, without logging in.

Read the original description

The BuddyForms plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.10.5 via a form-type confusion attack through the bf_post_type parameter. This is due to the public frontend submission handler buddyforms_form_response_no_ajax() authorizing logged-out submissions based solely on the target form's public_submit flag while independently trusting the attacker-supplied $_POST['bf_post_type'] to determine the post type of the newly created object — a cross-check introduced in 2.10.2 applies only to existing posts (post_id != 0) and is completely bypassed for new-object creation — combined with the save_post listener buddyforms_edit_form_save_meta_box_data() lacking both a current_user_can() capability check and a form-builder nonce, causing it to unconditionally persist attacker-supplied $_POST['buddyforms_options'] for any newly inserted buddyforms CPT post. This makes it possible for unauthenticated attackers to insert a rogue BuddyForms form configuration with an attacker-controlled new_user_role value into the live global form registry, then submit a registration through that form to create a new WordPress account with administrator-level privileges and achieve full site takeover. Exploitation requires the WordPress site to have "Anyone can register" enabled and at least one public BuddyForms form attached to a page, both of which are standard BuddyForms deployment configurations.

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 2.10.6.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Affected versions

  • themekraft BuddyForms

    through 2.10.5

Evidence 9

  1. Repository
  2. Link
  3. Link
  4. Link
  5. Link
Show all 9 sourcesShow fewer sources
  1. Link
  2. Link
  3. Link
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-107622

Is CVE-2026-107622 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-107622?

BuddyForms: through 2.10.5.Source: cve.now feed data

How do I fix CVE-2026-107622?

Upgrade BuddyForms to version 2.10.6, the fixed release. No workaround is listed in the checked facts.Source: github.com