B Blocks <= 2.0.6 - Missing Authorization to Unauthenticated Privilege Escalation via rgfr_registration Function
Strategic Overview
- Status
- Patched in 2.0.7
- Affected Plugin
- bBlocks – Essential Gutenberg Blocks & Patterns Collection
- Affected Version
<= 2.0.6- CVSS
- 9.8Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-8059
At a glance
CVE-2025-8059 is a critical-severity Missing Authorization vulnerability in the bBlocks WordPress plugin, affecting versions <= 2.0.6. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.7; sites on affected versions should update now. Disclosed August 2025, reported by Peter Thaleikis.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
bBlocks <= 2.0.6 carries this weakness at rgfr_registration(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For bBlocks the fix is 2.0.7: builds <= 2.0.6 are affected, anything from 2.0.7 onward is not.
Remediation
Update to version 2.0.7, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: bBlocks 2.0.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in bBlocks – Essential Gutenberg Blocks & Patterns Collection
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C