Contact Form by Bit Form <= 2.18.3 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload
Strategic Overview
- Status
- Patched in 2.18.4
- Affected Plugin
- Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder
- Affected Version
<= 2.18.3- CVSS
- 4.9Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2025-2580
At a glance
CVE-2025-2580 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Bit Form WordPress plugin, affecting versions <= 2.18.3. It carries a CVSS score of 4.9 (reachable over the network). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.18.4; sites on affected versions should update now. Disclosed April 2025, reported by Avraham Shemesh.
Vulnerability Overview
The Contact Form by Bit Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 2.18.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Bit Form <= 2.18.3 takes an account at Author level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Bit Form the fix is 2.18.4: builds <= 2.18.3 are affected, anything from 2.18.4 onward is not.
Remediation
Update to version 2.18.4, or a newer patched version
How does WordSec protect against this?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Bit Form 2.18.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2026-16573: Bit Form <= 3.1.0 Stored Cross-Site Scripting
CVE-2026-16573 - 7.2CVE-2024-47301: Bit Form – Contact Form Plugin <= 2.13.10 Stored XSS
CVE-2024-47301 - 5.5CVE-2024-7775: Contact Form by Bit… Arbitrary JavaScript File Uploads
CVE-2024-7775 - 4.4CVE-2025-15669: Bit Form Stored XSS
CVE-2025-15669
Other vulnerabilities in Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder
- 9.8CVE-2025-6679: Contact Form by Bit Form… Arbitrary File Upload
CVE-2025-6679 - 9.8CVE-2022-4774: Bit Form <= 1.8.1 Arbitrary File Upload to RCE
CVE-2022-4774 - 9.0CVE-2024-7777: Contact Form by Bit… Arbitrary File Read And Deletion
CVE-2024-7777 - 8.7CVE-2024-7782: Contact Form by Bit Form Authenticater
CVE-2024-7782 - 7.5CVE-2026-13693: Bit Form <= 3.0.0 Arbitrary File Read
CVE-2026-13693 - 7.2CVE-2025-30885: Bit Form – Contact Form Plugin <= 2.18.0 Open Redirect
CVE-2025-30885 - 7.2CVE-2024-47319: Bit Form – Contact Form Plugin Arbitrary File Upload
CVE-2024-47319 - 7.2CVE-2024-7702: Contact Form by Bit Form SQL Injection
CVE-2024-7702
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C