Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running BuddyForms <2.10.3
-
DeliverySend unauthenticated export request for a form
-
ExploitRetrieve form configuration lacking authorization check
-
ExecutionHarvest notification emails and reCAPTCHA secret key
-
ImpactAbuse leaked secrets for bypass or targeting
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions beyond the plugin being installed and active - remote unauthenticated exploitation against default configurations of the BuddyForms WordPress plugin before 2.10.3, with no user interaction or authentication required (AV:N/PR:N/UI:N). The meaningfulness of the disclosure is bounded by what the target has configured: the leaked data is only valuable where a form actually stores sensitive settings such as notification recipient email addresses or a reCAPTCHA secret key. Sites running 2.10.3 or later are not affected. There is no required privilege level or non-default mode acting as a limiting factor, which is why the flaw is easily automatable at scale. |
| Impact | This is a genuine but moderate-priority information-disclosure flaw, and the signals are internally consistent rather than conflicting. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms remote, unauthenticated, low-complexity access with no user interaction, matching the description's claim that unauthenticated users can download any form's stored configuration. Impact is capped at C:L/I:N/A:N - read-only exposure of configuration secrets, no write or availability effect. The SSVC framework aligns with a measured response: Exploitation=none (no observed in-the-wild activity), Automatable=yes (the request can be scripted against many sites), Technical Impact=partial. EPSS is low at 0.15% (4th percentile), and there is no CISA KEV listing, so there is no evidence of active or widespread exploitation despite the easy, automatable attack surface. The vuln.today 'this_month' decision label reflects this: worth patching on a normal cycle, not an emergency. The practical risk is elevated above a typical 5.3 because the leaked data - notification recipient email addresses and reCAPTCHA secret keys - can enable follow-on abuse (bypassing reCAPTCHA protection, spam/phishing targeting). Net: a real priority to patch but not a drop-everything issue; the Automatable=yes signal means it could be swept at scale if an exploit is published, so do not let the low EPSS alone defer it. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted request to the BuddyForms export endpoint on a target WordPress site and retrieves a form's full stored configuration without any permission check. The returned settings expose notification recipient email addresses and the site's reCAPTCHA secret key, which the attacker can then use to defeat the form's bot protection or to target the exposed addresses. Exploitation requires no authentication, no user interaction, and low attack complexity (AV:N/AC:L/PR:N/UI:N), making it trivially scriptable, though no confirmed public exploit code is identified in the provided sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
Unauthenticated information disclosure in the BuddyForms WordPress plugin before 2.10.3 lets remote attackers export any form's stored configuration without an authorization check, exposing notification recipient email addresses and reCAPTCHA secret keys that are not shown on the public form. The flaw is remotely reachable with no authentication or user interaction (CVSS 5.3, confidentiality-only impact) and is rated automatable under SSVC, but exploitation is assessed as none, no public exploit was identified at time of analysis, and EPSS is low at 0.15% (4th percentile). Sites running BuddyForms 2.10.3 or later are unaffected.
RemediationAI
Upgrade the BuddyForms plugin to 2.10.3 or later, the vendor-released patch version; the fix is documented in the WPScan advisory at https://wpscan.com/vulnerability/748ac082-c2cf-4fbf-b41f-363dc881a30e/ and tracked in NVD at https://nvd.nist.gov/vuln/detail/CVE-2026-118100. After updating, rotate any reCAPTCHA secret keys held in form settings and review notification recipient addresses on sites that ran a vulnerable version, since the issue is confidentiality-only and no integrity impact is assessed. No separate workaround is documented in the available sources; where an update cannot be applied immediately, restricting access to the plugin's form-export path at the web server or WAF layer would reduce exposure but risks breaking legitimate administrative exports.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
BuddyForms is a WordPress plugin used to build and manage front-end forms and their settings. The root cause is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): the form-configuration export routine fails to verify that the requester has the capability to manage the form being exported, so an unauthenticated request can retrieve settings that would normally be visible only to an administrator. The disclosed payload includes notification recipient email addresses and reCAPTCHA secret keys, neither of which is rendered on the public form. Because the missing check is on the export path rather than in the rendering layer, exposure applies to any active form whose stored settings contain these values; the flaw is not a sanitization or template issue and does not depend on a non-default plugin mode. No CPE identifiers were supplied; EUVD records the affected range as BuddyForms 0 through <2.10.3. The trigger is the export request itself bypassing the authorization check, and the SSVC assessment marks the issue automatable with partial technical impact.
Know when WordPress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Remote unauthenticated request with no user interaction yields PR:N/UI:N/AV:N/AC:L; read-only exposure of configuration secrets is C:L with no integrity or availability impact.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The BuddyForms WordPress plugin before 2.10.3 does not check that the requester is allowed to manage a form before exporting its configuration, allowing unauthenticated users to download any form's stored settings, including notification recipient email addresses and reCAPTCHA secret keys that are not shown on the public form.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-113730
GHSA-87rp-9h85-83hj
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB