The BuddyForms WordPress plugin before 2.10.3 does not check that the requester is allowed to manage a form before
Source GCVE Database
Not known to be exploited : upgrade to 2.10.3 soon.
Data as of 30 Oct 2026, 07:02 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.10.3
Exploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade BuddyForms (WordPress plugin) to 2.10.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BuddyForms | Affected
| Fixed in
|
AI-suggested
Upgrade the BuddyForms plugin to version 2.10.3 or later, where proper authorization checks have been implemented to restrict form configuration exports to authorized users only. No other mitigation is indicated by the available data.
Description
A vulnerability in the BuddyForms WordPress plugin versions prior to 2.10.3 allows unauthenticated users to export and download the configuration of any form without proper authorization checks. This exposure includes sensitive data such as notification recipient email addresses and reCAPTCHA secret keys that are not publicly visible on the form.