dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-1435

MEDIUM · 6.3 CVSS v3.1 Published 2025-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

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 bbPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.6.11. This is due to missing or incorrect nonce validation on the bbp_user_add_role_on_register() function. This makes it possible for unauthenticated attackers to elevate their privileges to that of a bbPress Keymaster via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Rather than implementing a nonce check to provide protection against this vulnerability, which would break functionality, the plugin no longer makes it possible to select a role during registration.

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 bbPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to 2.6.11 due to missing nonce validation in the bbp_user_add_role_on_register() function. This allows unauthenticated attackers to forge administrative requests and elevate their privileges to bbPress Keymaster by tricking site administrators into clicking malicious links.

MitigationUpgrade to bbPress version 2.6.12 or later, which removes the role selection capability during user registration to eliminate the CSRF attack surface.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

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 bbPress plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for bbPress in the list. Alternatively, check for /wp-content/plugins/bbpress/ directory on the server.
    Affected if bbPress plugin is present and active on the WordPress site
  2. Determine installed bbPress version
    In WordPress admin under Plugins, find bbPress and view the version number displayed. Or read the version from the main plugin file comment block at /wp-content/plugins/bbpress/bbpress.php.
    Affected if Version is 2.6.11 or lower (any version up to and including 2.6.11)
  3. Check if WordPress user registration is enabled
    In WordPress admin, go to Settings > General and verify the 'Membership' setting shows 'Anyone can register' is checked.
    Affected if User registration is enabled on the WordPress site
  4. Verify bbPress role assignment on registration
    In WordPress admin, go to Settings > bbPress and check the 'Default Role' setting. If a role is assigned during registration, the vulnerable function bbp_user_add_role_on_register() processes it.
    Affected if A default bbPress role (such as Keymaster, Moderator, or Participant) is configured for new users

The site is affected if bbPress version 2.6.11 or lower is installed AND WordPress user registration is enabled AND a bbPress role can be assigned during registration.

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

Upgrade to bbPress version 2.6.12 or later, which removes the role selection capability during user registration to eliminate the CSRF attack surface.

Recommended fix Moderate confidence

bbPress version 2.6.12 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the bbPress plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.6.12 or higher
  5. 5. Alternatively, manually download the latest version of bbPress from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the registration settings still meet your needs - note that role selection during registration is no longer available as part of the security fix
Caveat The ability to select a user role during registration has been removed as part of the security fix; site administrators will need to manually assign roles if needed

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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