dbcve.org
BuddyformsWordPress extension · Themekraft

CVE-2025-62973

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to after 2.9.0 or later.
See remediation →
62/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
Missing Authorization vulnerability in Themekraft BuddyForms buddyforms allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects BuddyForms: from n/a through <= 2.9.0.

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

Missing authorization vulnerability in the BuddyForms WordPress plugin allows unauthenticated or improperly authenticated users to access certain functionality that should be restricted by Access Control Lists (ACLs). The vulnerability exists in versions through 2.9.0, potentially enabling attackers to perform actions they should not have permission to execute.

MitigationUpdate BuddyForms to the latest patched version once available, or implement proper role-based access control (RBAC) checks around sensitive plugin functions to enforce authorization constraints.

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
BuddyformsWordPress extension
Affected:<= 2.9.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify BuddyForms plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'BuddyForms' or check the plugin file header for version. Alternatively, check /wp-content/plugins/buddyforms/readme.txt for the version line.
    Affected if The installed version is 2.9.0 or lower.
  2. Confirm plugin is active on the site
    In WordPress admin, go to Plugins > Installed Plugins and verify BuddyForms shows as 'Active'. Check wp_options table for option_name 'buddyforms_is_active' set to 1.
    Affected if The plugin is active and the vulnerability is reachable.
  3. Inspect ACL configuration settings
    Navigate to BuddyForms > Settings > Access Control or similar ACL settings page. Check if role-based access controls are properly configured for form submissions, entry management, or admin actions.
    Affected if ACL settings are missing, disabled, or improperly configured allowing unrestricted access to protected functions.
  4. Review user role assignments
    Check WordPress Users > All Users and compare assigned roles against BuddyForms role capabilities. Verify if any roles incorrectly have 'manage_options' or elevated BuddyForms capabilities.
    Affected if Users with insufficient privileges have been granted elevated BuddyForms capabilities or no role checks exist.
  5. Check for unauthenticated form endpoints
    Examine form submission URLs and AJAX endpoints used by BuddyForms (check /wp-admin/admin-ajax.php actions starting with 'buddyforms_'). Verify if these endpoints properly validate user authentication and authorization before processing requests.
    Affected if Form submission or AJAX endpoints can be accessed and processed without valid authentication or capability checks.

A user is affected if BuddyForms version 2.9.0 or lower is installed and active with missing or improperly configured Access Control List settings that allow unauthorized access to protected functionality.

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.

From vendor data
Upgrade available Upgrade to a release after 2.9.0
Interim mitigation

Update BuddyForms to the latest patched version once available, or implement proper role-based access control (RBAC) checks around sensitive plugin functions to enforce authorization constraints.

Fix this in Buddyforms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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