dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-6679

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Bit Form builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 2.20.4. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. For this to be exploitable, the PRO version needs to be installed and activated as well. Additionally a form with an advanced file upload element needs to be published.

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 builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in versions up to 2.20.4. Unauthenticated attackers can upload malicious files including executable code when the PRO version is active and a form with an advanced file upload element is published, potentially achieving remote code execution.

MitigationUpdate to Bit Form builder version 2.20.5 or later which includes proper file type validation. If immediate update is not possible, disable the PRO version and remove any published forms with advanced file upload elements as a temporary measure.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Bit Form plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Bit Form or Bit Form Pro. Check the version number listed. Alternatively, inspect the plugin header in /wp-content/plugins/bit-form/includes/plugin.php or similar main plugin file.
    Affected if Installed version is 2.20.4 or lower
  2. Confirm PRO version installation
    Check if the Bit Form PRO plugin is installed and activated. Look for 'Bit Form Pro' in the WordPress plugins list, or check for pro-specific files/folders like /wp-content/plugins/bit-form-pro/ or license-related settings in the plugin admin.
    Affected if PRO version is installed and activated (required for exploitation)
  3. Identify published forms with file upload
    In WordPress admin, navigate to Bit Form > All Forms. Review each published form and check if any contain a file upload field. Inspect the field settings to determine if it uses the 'advanced' file upload element type.
    Affected if A published form exists with an advanced file upload element enabled (required for exploitation)
  4. Verify file upload endpoint accessibility
    Check the site's published pages/posts for any containing Bit Form shortcodes with file upload fields. Test accessing the form submission URL (typically /?bitforms_submit=1 or similar endpoint) without authentication.
    Affected if A public-facing page contains a form with file upload capability

You are affected if Bit Form plugin version is 2.20.4 or lower, the PRO version is installed/activated, AND a form with an advanced file upload element is published on a public page.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to Bit Form builder version 2.20.5 or later which includes proper file type validation. If immediate update is not possible, disable the PRO version and remove any published forms with advanced file upload elements as a temporary measure.

Recommended fix Moderate confidence

Bit Form builder version 2.20.5 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Bit Form builder plugin
  4. Check the current version installed
  5. If version is 2.20.4 or below, update the plugin to the latest available version
  6. After updating, verify that the PRO version is also updated if applicable
  7. Ensure any published forms with advanced file upload elements are reviewed for security
Caveat Review form configurations after upgrade to ensure functionality is intact

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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