Radius Blocks – WordPress Gutenberg Blocks
radius-blocks · plugin
Known security vulnerabilities for Radius Blocks – WordPress Gutenberg Blocks. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
1 exploitable without logging in · 1 with public exploit code · latest Dec 18, 2025
Closed on wordpress.org
Removed from the directory on Aug 14, 2025 · reason: security issue. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 7.5
CVE-2025-32159login required≤ 2.2.1
WordPress Radius Blocks plugin <= 2.2.1 - Local File Inclusion vulnerability
- Medium 6.5
CVE-2024-54272login required≤ 2.1.2
WordPress Radius Blocks plugin <= 2.1.2 - Cross Site Scripting (XSS) vulnerability
- Medium 6.4
CVE-2025-5844contributor+≤ 2.2.1
Radius Blocks <= 2.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via subHeadingTagName Parameter
- Medium 5.4
CVE-2025-24712unauthenticated · needs a click≤ 2.1.2
WordPress Radius Blocks – WordPress Gutenberg Blocks Plugin <= 2.1.2 - Cross Site Request Forgery (CSRF) vulnerability
- Medium 4.3
CVE-2025-64282login required≤ 2.2.1
WordPress Radius Blocks plugin <= 2.2.1 - Insecure Direct Object References (IDOR) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).