Quick answers
- Is CVE-2026-107622 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107622 being exploited in the wild.
- How severe is CVE-2026-107622?
- Critical severity, with a CVSS score of 9.8, published 6 November 2026.
- Which products and versions are affected?
- Themekraft Buddyforms up to and including 2.10.5.
- Is there a fix for CVE-2026-107622?
- Yes: fixed in 2.10.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107622 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107622?
- Check whether you run Themekraft Buddyforms at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.10.6
Technical details
The vulnerability combines multiple authorization flaws: the frontend submission handler trusts the attacker-supplied `bf_post_type` POST parameter to determine the post type of newly created objects, while the `save_post` hook handler lacks both capability checks and nonce validation. An unauthenticated attacker can submit a public form with a crafted `bf_post_type` to create a rogue BuddyForms form post, then inject an attacker-controlled `new_user_role` value set to administrator, and finally register through that malicious form to achieve account creation with elevated privileges. The vulnerability affects all versions up to 2.10.5, with the form-type cross-check introduced in 2.10.2 only protecting existing posts, not new-object creation.
Affected products
- Themekraft BuddyForms up to and including 2.10.5
Timeline
- 2026-11-06: disclosed
- 2026-10-19: patched: Fix merged via PR #779 on October 19, 2026; release date of fixed version inferred from disclosure date