dbcve.org
Buddyboss PlatformWordPress extension · Buddyboss

CVE-2024-13402

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-27
Fix available
A fix is available. Upgrade to 2.8.00 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
The Buddyboss Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘link_title’ parameter in all versions up to, and including, 2.7.70 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Buddyboss Platform WordPress plugin up to version 2.7.70 suffers from a stored Cross-Site Scripting vulnerability in the 'link_title' parameter. Authenticated users with Subscriber-level permissions can inject arbitrary JavaScript through insufficient input sanitization, which executes when other users access the affected pages due to missing output escaping.

MitigationUpdate Buddyboss Platform to version newer than 2.7.70, or apply input sanitization (sanitize_text_field) and output escaping (esc_html/esc_attr) to the 'link_title' parameter.

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
Buddyboss PlatformWordPress extension
Affected:< 2.8.00

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. Check Buddyboss Platform version
    Go to WordPress admin dashboard > Plugins and find Buddyboss Platform in the list, or inspect the plugin header file (wp-content/plugins/buddyboss-platform/bp-loader.php) for the Version constant
    Affected if The installed version is 2.7.70 or any version below 2.8.00
  2. Confirm subscriber-level accounts exist
    Navigate to WordPress admin > Users and check if any users have the Subscriber role assigned, or verify if your site allows user registration that creates subscriber accounts
    Affected if Subscriber-level user accounts exist in the WordPress installation
  3. Check if link_title input field is accessible
    Examine Buddyboss Platform features that accept user-supplied link titles, such as activity posts, profile links, or social submission forms where users can submit a URL with a custom title
    Affected if The link_title parameter is accepted as user input in any Buddyboss feature
  4. Inspect output escaping for link_title
    Search the Buddyboss Platform plugin code for instances where link_title is displayed or echoed (look in bp-templates or activity files), and verify whether esc_html() or esc_attr() functions are used around the output
    Affected if The link_title value is output without esc_html or esc_attr escaping functions present in the code

You are affected if your installed Buddyboss Platform version is below 2.8.00 and the link_title parameter is used in your environment without proper output escaping.

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.00 or later
Fixed in 2.8.00
Interim mitigation

Update Buddyboss Platform to version newer than 2.7.70, or apply input sanitization (sanitize_text_field) and output escaping (esc_html/esc_attr) to the 'link_title' parameter.

Recommended fix High confidence

Buddyboss Platform version 2.8.00 or later

  1. Back up your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Buddyboss Platform
  3. If an update is available, click 'Update Now' to upgrade to version 2.8.00 or later
  4. Alternatively, you can manually download the latest version from buddyboss.com and upload it via WordPress > Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin version shows 2.8.00 or higher in Plugins list
  6. Clear any site caches if you use caching plugins

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

Fix this in Buddyboss Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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