On this page (7 sections)
A critical vulnerability, CVE-2026-107622, affects the BuddyForms plugin for WordPress in all versions up to and including 2.10.5. According to the GitHub advisory, an unauthenticated attacker can abuse the plugin's public form submission handling to end up with a new account that has administrator privileges, which means full site takeover.
If you run WordPress with open registration and a public BuddyForms form on any page, treat this as urgent. The advisory does not state a fixed version, so check the vendor's plugin page and changelog for the latest release, update to it, and use the exposure checks below while you confirm.
What happened
The flaw was published on November 6, 2026 through the National Vulnerability Database and the GitHub Advisory Database. The NVD entry repeats the same description, so there is effectively one source of technical detail so far. The GitHub advisory is marked as unreviewed and lists no package, so its affected and patched version fields show 'Unknown'. That reflects missing package data in GitHub's database, not a statement that no fix exists.
The advisory also links to a GitHub pull request, a WordPress.org Trac changeset and a Wordfence vulnerability entry. The research does not say which release contains a fix, so confirm the version number with the vendor rather than assuming.
How the weakness works, in plain terms
This is a privilege management problem (CWE-269). The plugin lets logged-out visitors submit certain public forms. According to the advisory, the submission handler decides whether to allow a logged-out submission based only on whether the target form is marked as publicly submittable. At the same time, it trusts a value supplied by the visitor to decide what type of content gets created.
A check added in version 2.10.2 compares the form and post type, but the advisory says it only applies to existing posts and is bypassed when a new object is created. A second problem sits in a listener that runs when a BuddyForms form-configuration post is saved. It lacks a capability check and a nonce, so it stores whatever configuration values the request supplies.
Combined, the advisory says an unauthenticated attacker can insert a rogue form configuration that sets which role new users receive, then register through that form and obtain an administrator account. We are deliberately not describing request details beyond what is needed to understand the risk.
Who is realistically exposed
The advisory states exploitation requires both of these conditions, and calls them standard BuddyForms deployment configurations:
- The WordPress setting 'Anyone can register' is enabled.
- At least one public BuddyForms form is attached to a page.
Sites that use BuddyForms for contact forms, user registration, directories or front-end posting are the most likely to match. Sites with registration disabled do not meet the stated precondition, though you should not rely on that alone as a long-term fix.
How to check your exposure
Start by confirming whether BuddyForms is installed and which version is running. This read-only WP-CLI command lists the plugin with its status and version. Run it from the WordPress root directory; any version at or below 2.10.5 is in the affected range.
wp plugin list --fields=name,status,version | grep -i buddyformsNext, check whether open registration is on. This read-only command prints 1 if 'Anyone can register' is enabled and 0 if it is not.
wp option get users_can_registerThen review your administrator accounts. This lists every user with the administrator role; look for names or email addresses you do not recognize and for recent registration dates.
wp user list --role=administrator --fields=ID,user_login,user_email,user_registeredWhat to do now
- Find every site you manage that has BuddyForms installed, including agency and client sites.
- Check the installed version; treat 2.10.5 and earlier as affected.
- Check the vendor's plugin page and changelog for the latest release, and update to a version that addresses CVE-2026-107622 as soon as you can confirm one.
- Until you can confirm a fix, turn off 'Anyone can register' under Settings > General if your site does not need it.
- If you cannot disable registration, consider deactivating BuddyForms or removing public forms from pages until a fix is confirmed.
- Review all administrator accounts and remove any you cannot account for.
- Review recently created content of the BuddyForms form type for configurations you did not create.
- If you find an unexpected administrator, follow a compromise response: reset passwords, rotate secrets and review for backdoors.
If you suspect an account was already created, our guides on checking whether a website is hacked and what to do after a compromise walk through the next steps.
Detection and monitoring afterwards
Because the outcome is a new administrator account, the most useful signals are inside WordPress: new users with elevated roles, unexpected changes to plugin or theme files, and new form configurations. Check your web server logs for unusual POST requests to pages hosting BuddyForms forms from unfamiliar IP addresses, and compare against your normal traffic.
Keeping a record of your plugin inventory and versions makes it much faster to respond to advisories like this one. The known WordPress plugin vulnerabilities page and our guide on checking whether a plugin is vulnerable can help. For broader hardening, see the WordPress security checklist.
What is still unknown
- Which plugin release fully resolves the issue. The advisory does not state a fixed version.
- Whether the flaw is being exploited in the wild. The research reports no exploitation, but it does not confirm a check against the CISA KEV catalog, so treat the status as unconfirmed.
- Independent confirmation. The GitHub advisory is unreviewed, and the NVD entry repeats its text.
We treat the technical description as the advisory's claim until the vendor or additional researchers confirm details. Given the critical score and low attack complexity, acting on the exposure checks now is reasonable even without confirmed exploitation.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
