dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-8059

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 B Blocks plugin for WordPress is vulnerable to Privilege Escalation due to missing authorization and improper input validation within the rgfr_registration() function in all versions up to, and including, 2.0.6. This makes it possible for unauthenticated attackers to create a new account and assign it the administrator role.

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 B Blocks WordPress plugin has a privilege escalation vulnerability in the rgfr_registration() function. Due to missing authorization checks and improper input validation, unauthenticated attackers can craft requests to create new WordPress user accounts with administrator-level privileges, giving them full site control.

MitigationUpdate the B Blocks plugin to the latest version immediately. If no patched version is available, deactivate the plugin until a fix is released, and disable user registration at the WordPress level as a defensive measure.

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
High
Integrity
High
Availability
High

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

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. Identify if B Blocks plugin is installed
    Navigate to WordPress admin > Plugins and look for 'B Blocks' in the list of installed plugins, or check the /wp-content/plugins/ directory for a folder named 'b-blocks' or similar
    Affected if The B Blocks plugin is present in the WordPress installation
  2. Determine the installed version of B Blocks
    In WordPress admin > Plugins, find B Blocks and note the version number displayed under the plugin name. Alternatively, check the main plugin PHP file header for the 'Version' tag
    Affected if The installed version is unknown, unpatched, or falls within a vulnerable version range
  3. Verify if WordPress user registration is enabled
    Go to WordPress admin > Settings > General and check 'Membership: Anyone can register' is enabled, or query the 'users_can_register' option via database or wp-cli
    Affected if User registration is enabled on the WordPress site (this enables the attack vector)
  4. Inspect for unauthorized administrator accounts
    Go to WordPress admin > Users and review all accounts with Administrator role. Check for unknown or suspicious admin accounts created recently, or query the wp_users and wp_usermeta tables for admin role users you did not create
    Affected if There are administrator accounts that were not created by legitimate administrators
  5. Review server access logs for registration function calls
    Search web server access logs (Apache/Nginx) for POST requests to /wp-admin/admin-ajax.php or the plugin's registration endpoint containing 'rgfr_registration' or unusual user registration activity from unauthenticated IPs
    Affected if There are requests to the vulnerable registration function from unauthenticated sources

A user is affected if B Blocks plugin is installed with a vulnerable version AND WordPress user registration is enabled, especially if unauthorized admin accounts exist.

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 B Blocks plugin to the latest version immediately. If no patched version is available, deactivate the plugin until a fix is released, and disable user registration at the WordPress level as a defensive measure.

Recommended fix High confidence

B Blocks plugin version > 2.0.6 (e.g., 2.0.7 or latest available version)

  1. Update the B Blocks plugin to the latest available version from the WordPress plugin repository
  2. After updating, review the list of users in WordPress admin under Users > All Users to check for any unauthorized administrator accounts
  3. If any suspicious administrator accounts are found that you did not create, delete them immediately
  4. Ensure WordPress user registration is properly configured if the rgfr_registration() function is needed, or disable registration if not needed

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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