dbcve.org
BuddyformsWordPress extension · Themekraft

CVE-2024-47377

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-05
Fix available
A fix is available. Upgrade to 2.8.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themekraft BuddyForms buddyforms allows Stored XSS.This issue affects BuddyForms: from n/a through <= 2.8.12.

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

A Stored Cross-Site Scripting (XSS) vulnerability exists in the BuddyForms WordPress plugin (versions up to 2.8.12) due to improper neutralization of user-supplied input during web page generation. This allows authenticated attackers to inject malicious JavaScript code into form submissions that persist and execute when other users (including administrators) view the affected content.

MitigationUpgrade BuddyForms to the latest version (beyond 2.8.12) which should contain proper input sanitization and output encoding. Until then, limit form submission permissions to trusted users only and implement Content Security Policy headers.

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

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'BuddyForms' or check the /wp-content/plugins/ directory for the buddyforms folder
    Affected if The plugin is not present in the WordPress installation
  2. Check installed BuddyForms version
    In WordPress admin, go to Plugins > Installed Plugins > BuddyForms and note the version number displayed, or check the buddyforms.php file header for the Version constant
    Affected if The installed version is lower than 2.8.13 (e.g., 2.8.12, 2.8.11, etc.)
  3. Confirm form submission capability is enabled
    In WordPress admin, go to BuddyForms > Forms and review which forms have the 'Submission' status set to 'open' or enabled for front-end submissions
    Affected if Any form allows public or untrusted user submissions; the vulnerability requires form data to be submitted and displayed
  4. Inspect form submission storage for suspicious content
    In WordPress admin, navigate to BuddyForms > Submissions and examine recent entries for unexpected script tags, javascript: URIs, or on* event handlers in text fields
    Affected if Form submissions contain unescaped HTML or JavaScript code that could execute in a browser when viewed

You are affected if BuddyForms is installed with a version below 2.8.13 and your forms accept submissions that are later displayed to other users.

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 2.8.13 or later
Fixed in 2.8.13
Interim mitigation

Upgrade BuddyForms to the latest version (beyond 2.8.12) which should contain proper input sanitization and output encoding. Until then, limit form submission permissions to trusted users only and implement Content Security Policy headers.

Recommended fix High confidence

Upgrade to BuddyForms version 2.8.13

  1. Backup your WordPress site and database before performing any plugin updates
  2. Navigate to WordPress Admin > Plugins > Installed Plugins
  3. Locate BuddyForms in the plugin list
  4. Click 'Update Now' to update BuddyForms to the latest version, or manually download version 2.8.13 from the WordPress plugin repository
  5. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins

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

Fix this in Buddyforms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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