Radius Blocks <= 2.2.1 - Authenticated (Subscriber+) Insecure Direct Object Reference
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Radius Blocks – WordPress Gutenberg Blocks
- Affected Version
<= 2.2.1- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2025-64282
At a glance
CVE-2025-64282 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Radius Blocks WordPress plugin, affecting versions <= 2.2.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed March 2025, reported by Tran Nguyen Bao Khanh.
Vulnerability Overview
The Radius Blocks – WordPress Gutenberg Blocks plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2.1 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.
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 interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Radius Blocks <= 2.2.1 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. No fixed build of this plugin is recorded for Radius Blocks yet, so installs running <= 2.2.1 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Radius Blocks – WordPress Gutenberg Blocks
- 8.8CVE-2025-32159: Radius Blocks <= 2.2.1 Local File Inclusion
CVE-2025-32159 - 6.4CVE-2025-5844: Radius Blocks <= 2.2.1 Stored Cross-Site Scripting
CVE-2025-5844 - 6.4CVE-2024-54272: Radius Blocks – WordPress Gutenberg Blocks Stored XSS
CVE-2024-54272 - 4.3CVE-2025-24712: Radius Blocks <= 2.1.2 Cross-Site Request Forgery
CVE-2025-24712
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C