dbcve.org
Activity Plus Reloaded For BuddypressWordPress extension · Buddydev

CVE-2024-11913

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 1.1.2 or later.
See remediation →
60/100
Remediation priority · Elevated
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
The Activity Plus Reloaded for BuddyPress plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 1.1.1 via the 'ajax_preview_link' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 Activity Plus Reloaded for BuddyPress WordPress plugin versions up to 1.1.1 contains a blind Server-Side Request Forgery (SSRF) vulnerability in the 'ajax_preview_link' function. Authenticated attackers with Subscriber-level permissions can manipulate the plugin to make arbitrary HTTP requests from the server, potentially enabling reconnaissance against internal infrastructure and services.

MitigationUpdate the plugin to a version beyond 1.1.1 if available, or implement strict allowlist-based validation on the 'ajax_preview_link' function to restrict requests to trusted domains only.

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
Activity Plus Reloaded For BuddypressWordPress extension
Affected:< 1.1.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Confirm plugin is installed
    Locate the 'buddydev-activity-plus-reloaded' plugin folder in your WordPress installation under wp-content/plugins/ and verify the plugin files exist, particularly any file containing 'ajax_preview_link' functionality
    Affected if The plugin folder exists and contains the vulnerable code
  2. Identify installed version
    Check the plugin header in the main plugin PHP file for the Version field, or query it via wp-cli: wp plugin get activity-plus-reloaded-for-buddypress --field=version
    Affected if Version is 1.1.1 or lower (any version below 1.1.2)
  3. Verify WordPress user registration is enabled
    Check WordPress general settings to confirm 'Membership' is set to allow anyone to register, or query the 'users_can_register' option via: wp option get users_can_register
    Affected if User registration is enabled, allowing potential attacker account creation
  4. Confirm Subscriber role exists
    Verify the Subscriber role is present and not disabled in your user roles configuration, or check that default roles include Subscriber
    Affected if Subscriber role is available to assigned users
  5. Check if ajax_preview_link endpoint is accessible
    Inspect the plugin source code for the ajax_preview_link function and verify it is hooked to a WordPress AJAX action (wp_ajax_ or wp_ajax_nopriv_) without additional capability checks beyond authenticated user status
    Affected if The endpoint is registered without restrictive capability checks and accepts requests from authenticated users

You are affected if the plugin version is 1.1.1 or lower and the ajax_preview_link function is accessible to authenticated users with Subscriber-level permissions.

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

Update the plugin to a version beyond 1.1.1 if available, or implement strict allowlist-based validation on the 'ajax_preview_link' function to restrict requests to trusted domains only.

Recommended fix High confidence

Activity Plus Reloaded for BuddyPress version 1.1.2

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'Activity Plus Reloaded for BuddyPress' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.1.2
  5. Verify the plugin is updated to version 1.1.2
Caveat Minor plugin version update; verify custom functionality works after upgrading

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

Fix this in Activity Plus Reloaded For Buddypress 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-11913 — 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-11913 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