dbcve.org
BuddyformsWordPress extension · Themekraft

CVE-2025-32151

HIGH · 8.8 CVSS v3.1 Published 2025-04-04
Fix available
A fix is available. Upgrade to after 2.8.15 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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Themekraft BuddyForms buddyforms allows PHP Local File Inclusion.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

The BuddyForms WordPress plugin versions <= 2.9.0 contains a PHP Local File Inclusion vulnerability due to improper control of filename parameters in include/require statements. Attackers could potentially include arbitrary local PHP files, potentially leading to remote code execution.

MitigationUpdate BuddyForms to the latest patched version once available. If no patch exists, disable the plugin and implement input validation/whitelisting on file inclusion functions, or remove the plugin until remediation is possible.

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.8.15

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. Locate the BuddyForms plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'buddyforms' or similar Themekraft BuddyForms installation.
    Affected if The BuddyForms plugin folder exists in the WordPress installation.
  2. Determine the installed BuddyForms version
    Open the main BuddyForms plugin file (usually buddyforms.php) and look for the 'Version:' header in the plugin comments, or check the readme.txt file for the 'Stable tag:' or version number.
    Affected if The version number displayed is <= 2.8.15 (or <= 2.9.0 per summary).
  3. Verify the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Check if BuddyForms shows as 'Active'.
    Affected if BuddyForms is currently activated on the WordPress site.
  4. Inspect for vulnerable file inclusion patterns
    Search the BuddyForms plugin files for include, require, include_once, or require_once statements that use unsanitized variables in the file path (e.g., include($_GET['file'])). Use grep or a code editor to scan PHP files in the plugin directory.
    Affected if Unsanitized file inclusion calls are found that could allow arbitrary file paths.

A user is affected if BuddyForms version is <= 2.8.15, the plugin is active, and vulnerable file inclusion code exists in the installation.

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.8.15
Interim mitigation

Update BuddyForms to the latest patched version once available. If no patch exists, disable the plugin and implement input validation/whitelisting on file inclusion functions, or remove the plugin until remediation is possible.

Recommended fix Moderate confidence

Latest version of BuddyForms (version higher than 2.9.0)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the BuddyForms plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Verify the update was successful by checking the plugin version after updating.
  6. 6. Test critical BuddyForms functionality (form submissions, front-end display) to ensure the update did not break existing functionality.
Caveat Minor or major version update may include changes to form rendering or API - test in staging environment first if possible

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

Fix this in Buddyforms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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