CVE-2025-5844: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in techlabpro1 Radius Blocks – WordPress Gutenberg Blocks
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.
AI Analysis
Technical Summary
CVE-2025-5844 is a stored Cross-Site Scripting (XSS) vulnerability identified in the Radius Blocks plugin for WordPress, specifically within the 'subHeadingTagName' parameter. This vulnerability exists due to insufficient sanitization and escaping of user-supplied input during web page generation, classified under CWE-79. The flaw allows authenticated users with Contributor-level permissions or higher to inject arbitrary JavaScript code into pages or posts. Because the malicious script is stored persistently, it executes every time the infected page is accessed by any user, including administrators and visitors. The vulnerability affects all versions up to and including 2.2.1 of the plugin. Exploitation requires no user interaction beyond viewing the compromised page but does require authenticated access with at least Contributor privileges, which are commonly granted to trusted users who can submit content. The CVSS v3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, privileges required, no user interaction, and a scope change. Although no known exploits have been reported in the wild, the vulnerability poses a significant risk due to the widespread use of WordPress and the Radius Blocks plugin in content management. The vulnerability could lead to session hijacking, privilege escalation, defacement, or distribution of malware through injected scripts. The lack of available patches at the time of disclosure necessitates immediate mitigation steps by administrators.
Potential Impact
The impact of CVE-2025-5844 is primarily on the confidentiality and integrity of affected WordPress sites. Successful exploitation allows attackers to execute arbitrary JavaScript in the context of the victim's browser, potentially stealing session cookies, redirecting users to malicious sites, or performing actions on behalf of users with elevated privileges. This can lead to unauthorized access, data leakage, defacement, or distribution of malware. Since the vulnerability requires Contributor-level access, insider threats or compromised contributor accounts pose a significant risk. The scope includes all websites using the Radius Blocks plugin up to version 2.2.1, which may be numerous given WordPress's market share. The vulnerability does not directly affect availability but can indirectly cause service disruption through defacement or administrative lockout. Organizations relying on WordPress for content management, especially those with multiple contributors, are at risk of targeted attacks exploiting this vulnerability to escalate privileges or compromise site integrity.
Mitigation Recommendations
To mitigate CVE-2025-5844, organizations should immediately audit user roles and permissions, restricting Contributor-level access to trusted users only. Implement strict input validation and output encoding for all user-supplied data, particularly the 'subHeadingTagName' parameter, to prevent script injection. Monitor and sanitize existing content for injected scripts. Since no official patch is currently available, consider temporarily disabling the Radius Blocks plugin or replacing it with alternative Gutenberg blocks that have been verified secure. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting this parameter. Regularly update WordPress core and plugins to incorporate security fixes once patches are released. Additionally, educate content contributors about safe content practices and monitor logs for unusual activity indicative of exploitation attempts.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2025-5844: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in techlabpro1 Radius Blocks – WordPress Gutenberg Blocks
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-5844 is a stored Cross-Site Scripting (XSS) vulnerability identified in the Radius Blocks plugin for WordPress, specifically within the 'subHeadingTagName' parameter. This vulnerability exists due to insufficient sanitization and escaping of user-supplied input during web page generation, classified under CWE-79. The flaw allows authenticated users with Contributor-level permissions or higher to inject arbitrary JavaScript code into pages or posts. Because the malicious script is stored persistently, it executes every time the infected page is accessed by any user, including administrators and visitors. The vulnerability affects all versions up to and including 2.2.1 of the plugin. Exploitation requires no user interaction beyond viewing the compromised page but does require authenticated access with at least Contributor privileges, which are commonly granted to trusted users who can submit content. The CVSS v3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, privileges required, no user interaction, and a scope change. Although no known exploits have been reported in the wild, the vulnerability poses a significant risk due to the widespread use of WordPress and the Radius Blocks plugin in content management. The vulnerability could lead to session hijacking, privilege escalation, defacement, or distribution of malware through injected scripts. The lack of available patches at the time of disclosure necessitates immediate mitigation steps by administrators.
Potential Impact
The impact of CVE-2025-5844 is primarily on the confidentiality and integrity of affected WordPress sites. Successful exploitation allows attackers to execute arbitrary JavaScript in the context of the victim's browser, potentially stealing session cookies, redirecting users to malicious sites, or performing actions on behalf of users with elevated privileges. This can lead to unauthorized access, data leakage, defacement, or distribution of malware. Since the vulnerability requires Contributor-level access, insider threats or compromised contributor accounts pose a significant risk. The scope includes all websites using the Radius Blocks plugin up to version 2.2.1, which may be numerous given WordPress's market share. The vulnerability does not directly affect availability but can indirectly cause service disruption through defacement or administrative lockout. Organizations relying on WordPress for content management, especially those with multiple contributors, are at risk of targeted attacks exploiting this vulnerability to escalate privileges or compromise site integrity.
Mitigation Recommendations
To mitigate CVE-2025-5844, organizations should immediately audit user roles and permissions, restricting Contributor-level access to trusted users only. Implement strict input validation and output encoding for all user-supplied data, particularly the 'subHeadingTagName' parameter, to prevent script injection. Monitor and sanitize existing content for injected scripts. Since no official patch is currently available, consider temporarily disabling the Radius Blocks plugin or replacing it with alternative Gutenberg blocks that have been verified secure. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting this parameter. Regularly update WordPress core and plugins to incorporate security fixes once patches are released. Additionally, educate content contributors about safe content practices and monitor logs for unusual activity indicative of exploitation attempts.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-06-06T22:43:06.913Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 689ef436ad5a09ad0069732b
Added to database: 8/15/2025, 8:47:50 AM
Last enriched: 2/27/2026, 3:38:00 PM
Last updated: 3/21/2026, 8:05:36 AM
Views: 57
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.