dbcve.org
Bit FormWordPress extension · Bitapps

CVE-2024-43249

HIGH · 8.8 CVSS v3.1 Published 2024-08-19
Fix available
A fix is available. Upgrade to after 2.6.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Unrestricted Upload of File with Dangerous Type vulnerability in Bit Apps Bit Form Pro allows Command Injection.This issue affects Bit Form Pro: from n/a through 2.6.4.

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 · moderate confidence

This is an unrestricted file upload vulnerability in Bit Apps Bit Form Pro plugin (likely WordPress) that allows attackers to upload malicious files (such as PHP scripts) and execute arbitrary commands on the server. The lack of proper file type validation and secure file handling enables remote code execution.

MitigationUpdate Bit Form Pro to version 2.6.5 or later. Until patched, disable file upload forms or implement web server-level restrictions to prevent execution of uploaded files.

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
Bit FormWordPress extension
Affected:<= 2.6.4

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Bit Form' or 'Bit Form Pro' in the list of active plugins.
    Affected if The Bit Form or Bit Form Pro plugin appears in the installed plugins list.
  2. Check installed version number
    In the WordPress plugins list, click on the plugin to view its details, or check the plugin header comment in the main PHP file (typically in /wp-content/plugins/bit-form/). Compare the version shown against the affected range.
    Affected if The installed version is 2.6.4 or lower.
  3. Identify if file upload fields exist in any form
    In the WordPress admin, go to Bit Form > All Forms and review each form. Check if any form contains a file upload input field (usually labeled 'File Upload' or similar).
    Affected if Any form contains an enabled file upload input field.
  4. Verify uploaded file storage location
    Inspect the form settings for file upload fields. Check if files are stored in a web-accessible directory without execution prevention (such as missing .htaccess restrictions in the upload folder).
    Affected if Uploaded files are stored in a web-accessible folder that allows script execution.

A user is affected if Bit Form plugin version 2.6.4 or lower is installed AND any form contains an enabled file upload field with files stored in an executable location.

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 a release after 2.6.4
Interim mitigation

Update Bit Form Pro to version 2.6.5 or later. Until patched, disable file upload forms or implement web server-level restrictions to prevent execution of uploaded files.

Recommended fix Moderate confidence

Version higher than 2.6.4 (e.g., 2.7.0 or later)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate Bit Form Pro in the plugin list
  4. 4. Check if an update is available for Bit Form Pro
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the updated version from the official WordPress plugin repository or your purchase source
  7. 7. After updating, verify the form functionality works as expected
  8. 8. Test file upload forms to ensure the vulnerability is remediated

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

Fix this in Bit Form Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43249 — 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-43249 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