dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12391

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Restrictions for BuddyPress plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the handle_optin_optout() function in all versions up to, and including, 1.5.2. This makes it possible for unauthenticated attackers to opt in and out of tracking.

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 Restrictions for BuddyPress WordPress plugin lacks a capability check in the handle_optin_optout() function, allowing unauthenticated users to modify tracking opt-in/opt-out settings. This is a classic IDOR/privilege escalation vulnerability where an AJAX or form handler accepts requests from any visitor without verifying user permissions.

MitigationUpdate the plugin to version 1.5.3 or later which includes proper capability checks. If immediate update is not possible, restrict access to the affected endpoint at the web server level or disable the plugin until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 installation
    Navigate to WordPress admin > Plugins and locate 'Restrictions for BuddyPress' in the list of installed plugins. Verify it is activated.
    Affected if The plugin is installed and active in WordPress.
  2. Identify installed version
    In the Plugins list, click on the plugin name to view details, or inspect the plugin main file header in wp-content/plugins/restrictions-for-buddypress/ for the 'Version' field.
    Affected if The installed version is lower than the patched version (your environment team should know the specific threshold).
  3. Check for vulnerable function in code
    Inspect the plugin file containing handle_optin_optout() (typically in includes/ or main plugin file). Look for the function definition and verify if it lacks current_user_can() or similar capability checks before processing the request.
    Affected if The handle_optin_optout() function exists without capability verification logic.
  4. Test endpoint accessibility
    Send a crafted request to the AJAX endpoint or form handler that invokes handle_optin_optout() (commonly at wp-admin/admin-ajax.php or a front-end AJAX URL) without providing valid authentication credentials. Observe if the request is processed.
    Affected if The endpoint accepts and processes requests from unauthenticated visitors without returning an authorization error.
  5. Verify tracking feature configuration
    Access the plugin settings page in WordPress admin under BuddyPress or plugin-specific settings. Check if any tracking, opt-in, or opt-out related features are enabled or configurable.
    Affected if Tracking-related settings are present and the feature is accessible to users.

A user is affected if the plugin is installed with a version lacking the capability fix AND the vulnerable endpoint processes unauthenticated requests to modify tracking settings.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.5.3 or later which includes proper capability checks. If immediate update is not possible, restrict access to the affected endpoint at the web server level or disable the plugin until patched.

Recommended fix Moderate confidence

Version higher than 1.5.2 (check wordpress.org for the latest stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Restrictions for BuddyPress' in the plugin list
  4. Check if an update is available and update to the latest version (version higher than 1.5.2)
  5. Alternatively, download the latest version from wordpress.org/plugins/restrictions-for-buddypress/ and upload via Plugins > Add New > Upload Plugin

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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