Plugins · radius-blocks · data as of 2026-11-04
Is Radius Blocks safe? Known vulnerabilities and latest version
- Status
- Closed 2025-08-14
- Known issues on record
- 5
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate radius-blocks && wp plugin delete radius-blocks
Check your version
Known vulnerabilities
5 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 5 record(s) do not state which versions are affected.
medium 4.3 CVE-2025-64282 · published 2025-12-18
Missing authorization check in Radius Blocks (2.2.1 and older)
- Affected
- 2.2.1 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Authorization Bypass Through User-Controlled Key vulnerability in RadiusTheme Radius Blocks radius-blocks allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Radius Blocks: from n/a through <= 2.2.1.
medium 6.4 CVE-2025-5844 · published 2025-08-15
Stored cross-site scripting (XSS) in Radius Blocks (2.2.1 and older)
- Affected
- 2.2.1 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Radius Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘subHeadingTagName’ parameter in all versions up to, and including, 2.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
NVD CVE-2025-5844Wordfence advisorywordpress.orgPlugin source
high 7.5 CVE-2025-32159 · published 2025-04-04
File inclusion in Radius Blocks (2.2.1 and older)
- Affected
- 2.2.1 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in RadiusTheme Radius Blocks radius-blocks allows PHP Local File Inclusion.This issue affects Radius Blocks: from n/a through <= 2.2.1.
medium 5.4 CVE-2025-24712 · published 2025-01-24
Cross-site request forgery (CSRF) in Radius Blocks (2.1.2 and older)
- Affected
- 2.1.2 and older
- Fixed in
- 2.2.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in RadiusTheme Radius Blocks radius-blocks allows Cross Site Request Forgery.This issue affects Radius Blocks: from n/a through <= 2.1.2.
medium 6.5 CVE-2024-54272 · published 2024-12-13
Stored cross-site scripting (XSS) in Radius Blocks (2.1.2 and older)
- Affected
- 2.1.2 and older
- Fixed in
- 2.2.0
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in RadiusTheme Radius Blocks radius-blocks allows Stored XSS.This issue affects Radius Blocks: from n/a through <= 2.1.2.
Recent activity
- 2025-08-14 — closed on wordpress.org (Security Issue).
- 2025-12-18 — Missing authorization check disclosed (CVE-2025-64282), fix version not stated.
- 2025-08-15 — Stored cross-site scripting (XSS) disclosed (CVE-2025-5844), fix version not stated.
- 2025-04-04 — File inclusion disclosed (CVE-2025-32159), fix version not stated.
Get an email when Radius Blocks has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Radius Blocks (radius-blocks) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (2) · Missing authorization (1) · File inclusion (1) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/radius-blocks (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/radius-blocks"><img src="https://laskyr.com/plugins/radius-blocks/badge.svg" alt="Radius Blocks vulnerability status"></a>