PatchSiren cyber security CVE debrief
CVE-2025-15669 Bit Form CVE debrief
The Bit Form WordPress plugin before 3.1.4 does not sanitise one of its conversational-form display settings before rendering it on the public-facing form, allowing high-privilege users to store JavaScript that executes in the browser of any visitor who views the form. This vulnerability requires verification of plugin version and conversational-form display settings to prevent exploitation. Affected administrators should assess exposure and verify the plugin version to address this issue.
- Vendor
- Bit Form
- Product
- Bit Form WordPress plugin
- CVSS
- MEDIUM 4.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-01
- Original CVE updated
- 2026-09-29
- Advisory published
- 2026-08-01
- Advisory updated
- 2026-09-29
Who should care
Administrators of WordPress installations using the Bit Form plugin should assess exposure and verify the plugin version. They should review and sanitize conversational-form display settings to prevent exploitation. Security teams and vulnerability management teams should also review this vulnerability and plan for remediation if necessary.
Why it matters
CVE-2025-15669 allows high-privilege users to store JavaScript that executes in visitors' browsers, requiring verification of plugin version and conversational-form display settings.
- Stored JavaScript can execute in visitors' browsers
- High-privilege users can store malicious JavaScript
- Public-facing forms may be used to exploit this vulnerability
- Verification of plugin version and conversational-form display settings is necessary
Technical summary
The Bit Form WordPress plugin before 3.1.4 does not sanitise one of its conversational-form display settings before rendering it on the public-facing form, allowing high-privilege users (such as administrators) to store JavaScript that executes in the browser of any visitor who views the form. This vulnerability requires verification of plugin version and conversational-form display settings to prevent exploitation. Affected administrators should assess exposure and verify the plugin version to address this issue. The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 4.8 and MEDIUM severity.
Defensive priority
Administrators of WordPress installations using the Bit Form plugin should verify the plugin version and update to 3.1.4 or later to address this issue.
Recommended defensive actions
- Verify the Bit Form plugin version and update to 3.1.4 or later
- Review and sanitize conversational-form display settings
- Monitor for suspicious JavaScript execution on public-facing forms
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 4.8 and MEDIUM severity. A WPScan vulnerability advisory explicitly names the Bit Form WordPress plugin as affected.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-15669 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-15669
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-15669 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-15669
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/69800fa9-4fbd-489c-8759-96df745d77d6/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.