CVE-2025-30885

Bit Form – Contact Form Plugin <= 2.18.0 - Open Redirect

2025-03-27 00:00
Le Ngoc Anh

Strategic Overview

Status
Patched in 2.18.1
Affected Version
<= 2.18.0
CVSS
7.2High
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2025-30885
View all Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder vulnerabilities

At a glance

CVE-2025-30885 is a high-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Bit Form WordPress plugin, affecting versions <= 2.18.0. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.18.1; sites on affected versions should update now. Disclosed March 2025, reported by Le Ngoc Anh.

Vulnerability Overview

The Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 2.18.0. This is due to insufficient validation on a redirect url. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

Reaching this weakness in Bit Form <= 2.18.0 takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For Bit Form the fix is 2.18.1: builds <= 2.18.0 are affected, anything from 2.18.1 onward is not.

Remediation

Update to version 2.18.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Bit Form: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Bit Form 2.18.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C