dbcve.org
Buddyboss PlatformWordPress extension · Buddyboss

CVE-2024-13858

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-02
Fix available
A fix is available. Upgrade to after 2.8.50 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 and BuddyBoss Theme for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘invitee_name’ parameter in all versions up to, and including, 2.8.50 and 2.8.41, respectively, 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. The vulnerability was partially patched in the BuddyBoss Platform plugin in version 2.8.41.

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 plugin and Theme for WordPress are vulnerable to Stored Cross-Site Scripting (XSS) via the 'invitee_name' parameter due to insufficient input sanitization and output escaping. Authenticated attackers with Subscriber-level access can inject arbitrary JavaScript that executes when other users access the affected page. The vulnerability affects platform versions up to 2.8.50 and theme versions up to 2.8.41.

MitigationUpdate the BuddyBoss Platform plugin to version 2.8.41 or later and ensure the theme is updated accordingly. Apply proper input sanitization and output escaping for the invitee_name parameter as a defense-in-depth measure.

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

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
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > BuddyBoss Platform and view the version number, or check the version in the plugin header file via file system access
    Affected if The installed version is 2.8.50 or lower (any version up to and including 2.8.50)
  2. Verify BuddyBoss Platform is active
    Confirm the BuddyBoss Platform plugin is installed and active on the WordPress site
    Affected if The plugin is active and the version check above shows an affected version
  3. Confirm invitation/connection feature is enabled
    Check if BuddyBoss social features that use the invitee_name parameter (such as friend requests, group invitations, or connection invitations) are enabled in the platform settings under BuddyPress components
    Affected if Any invitation or connection feature that accepts the invitee_name parameter is active on the site
  4. Locate vulnerable parameter handling in code
    Search plugin source files for handling of the invitee_name parameter, specifically looking for instances where this input is used without proper sanitization via functions like sanitize_text_field or esc_html/escape functions
    Affected if Code inspection reveals invitee_name is processed without sanitization and output escaping before being stored or displayed

The environment is affected if BuddyBoss Platform version 2.8.50 or lower is installed and active, and the invitation/connection feature that uses invitee_name is enabled on the site.

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

Update the BuddyBoss Platform plugin to version 2.8.41 or later and ensure the theme is updated accordingly. Apply proper input sanitization and output escaping for the invitee_name parameter as a defense-in-depth measure.

Recommended fix Moderate confidence

BuddyBoss Platform > 2.8.50 (latest available version); BuddyBoss Theme > 2.8.41 (latest available version)

  1. 1. Log in to your WordPress admin dashboard.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate 'BuddyBoss Platform' in the plugin list.
  4. 4. Check the current version number displayed under the plugin name.
  5. 5. Navigate to Dashboard > Updates to check for available updates, or visit the BuddyBoss website to download the latest version.
  6. 6. If an update is available, click 'Update Now' on the BuddyBoss Platform plugin.
  7. 7. After updating, verify the version number has increased beyond 2.8.50.
  8. 8. If you also use the BuddyBoss Theme, repeat the update process for the theme, ensuring it is updated beyond version 2.8.41.
Caveat Standard WordPress plugin/theme update best practices apply - backup your site before updating

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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