dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14901

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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 – Contact Form Plugin plugin for WordPress is vulnerable to unauthorized workflow execution due to missing authorization in the triggerWorkFlow function in all versions up to, and including, 2.21.6. This is due to a logic flaw in the nonce verification where the security check only blocks requests when both the nonce verification fails and the user is logged in. This makes it possible for unauthenticated attackers to replay form workflow executions and trigger all configured integrations including webhooks, email notifications, CRM integrations, and automation platforms via the bitforms_trigger_workflow AJAX action granted they can obtain the entry ID and log IDs from a legitimate form submission response.

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 has a logic flaw in its triggerWorkFlow function where nonce verification is only enforced when the user is logged in. The flawed condition checks (nonce_fails AND logged_in) instead of just verifying the nonce, allowing unauthenticated attackers to replay form submissions by obtaining entry ID and log IDs from legitimate form responses, then triggering the bitforms_trigger_workflow AJAX action to execute all configured integrations (webhooks, emails, CRM, automation).

MitigationUpdate to version 2.21.7 or later which properly validates nonces regardless of authentication status, and ensure proper authorization checks are in place for workflow triggering.

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
None
Integrity
Low
Availability
Low

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

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. Verify Bit Form plugin is installed
    Check your WordPress installation's plugin directory for 'bit-form' or 'Bit Form' plugin, or query the wp_options table for the active_plugins entry. Note the installed version number.
    Affected if The plugin is installed and active on the WordPress site
  2. Compare installed version to patched release
    Locate the plugin version in the plugin header (typically in the main PHP file comment) or via WordPress admin plugins page. Compare against version 2.21.7.
    Affected if The installed version is prior to 2.21.7 (versions 2.21.6 and earlier are likely vulnerable)
  3. Confirm workflow integrations are configured
    Check if any workflows, webhooks, email actions, CRM connections, or automation rules are active in the Bit Form settings. Look in the WordPress admin under Bit Form > Workflows or similar integration settings.
    Affected if One or more workflow integrations (webhooks, emails, CRM, automations) are configured and active in the plugin
  4. Verify AJAX endpoint exposure
    Confirm the WordPress site has the AJAX handler accessible at /wp-admin/admin-ajax.php. Test if the 'bitforms_trigger_workflow' action is registered by checking plugin code or probing the endpoint with a nonce test.
    Affected if The bitforms_trigger_workflow AJAX action is registered and accessible without authentication
  5. Inspect triggerWorkFlow function for conditional nonce check
    Locate the triggerWorkFlow function in the plugin code (typically in includes/Workflow.php or similar). Examine the nonce verification logic to confirm it only triggers when (nonce_fails AND logged_in) rather than always validating the nonce.
    Affected if The code shows nonce validation is gated behind a logged_in_user check rather than performed unconditionally

You are affected if Bit Form plugin versions prior to 2.21.7 are installed with active workflow integrations and the vulnerable triggerWorkFlow function permits unauthenticated AJAX requests.

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 version 2.21.7 or later which properly validates nonces regardless of authentication status, and ensure proper authorization checks are in place for workflow triggering.

Recommended fix High confidence

Version 2.21.7 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Bit Form plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/bit-form and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the version number reflects the patched release (2.21.7 or later)
  7. 7. Test form submissions to confirm the workflow trigger function operates correctly

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

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

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-2025-14901 — 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-14901 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