dbcve.org
Contact Form BuilderWordPress extension · Bitapps

CVE-2024-13450

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-25
Fix available
A fix is available. Upgrade to 2.17.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 Server-Side Request Forgery in all versions up to, and including, 2.17.4 via the Webhooks integration. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The vulnerability can also be exploited in Multisite environments.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Bit Form WordPress plugin versions up to 2.17.4 contains an SSRF vulnerability in its Webhooks integration that allows authenticated administrators to make arbitrary HTTP requests from the server, potentially querying and modifying data from internal services or internal-only URLs.

MitigationUpdate to version 2.17.5 or later which contains the patch; restrict administrator-level user capabilities and monitor for suspicious requests to internal IP addresses or local network addresses in the meantime.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Contact Form BuilderWordPress extension
Affected:< 2.17.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Bit Form plugin is installed
    Check for the presence of the 'bit-form' or 'bitapps-contact-form-builder' directory in /wp-content/plugins/ on the server, or view the installed plugins list in the WordPress admin dashboard under Plugins.
    Affected if The plugin directory exists in the WordPress plugins folder.
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed for 'Bit Form' or 'Bitapps Contact Form Builder'. Alternatively, open the main plugin PHP file (such as bit-form.php) and look for the 'Version' header in the plugin comment block.
    Affected if The displayed version is below 2.17.5 (for example: 2.17.4, 2.17.3, 2.16.x, etc.).
  3. Verify Webhooks integration is configured
    In the WordPress admin panel, navigate to the Bit Form plugin settings. Look for a Webhooks or Integrations section within the form builder settings. Check if any webhook endpoints have been added or configured.
    Affected if Webhooks have been set up in the plugin, as the SSRF vulnerability exists specifically within the Webhooks integration feature.

You are affected if the Bit Form plugin is installed with a version lower than 2.17.5 and the Webhooks integration feature has been configured or enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.17.5 or later
Fixed in 2.17.5
Interim mitigation

Update to version 2.17.5 or later which contains the patch; restrict administrator-level user capabilities and monitor for suspicious requests to internal IP addresses or local network addresses in the meantime.

Recommended fix High confidence

2.17.5

  1. 1. Log in to the WordPress admin dashboard with Administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Contact Form by Bit Form' plugin in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to version 2.17.5 or later
  5. 5. Alternatively, go to Plugins > Add New > Upload Plugin and upload the latest version from the WordPress plugin repository
  6. 6. After updating, verify the plugin version shows 2.17.5 or higher under Plugins > Installed Plugins
  7. 7. Test the Webhooks integration functionality to ensure it continues to work properly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Contact Form Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13450 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data