Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11878: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in beautifultemplates ST Categories Widget

0
Medium
VulnerabilityCVE-2025-11878cvecve-2025-11878cwe-79
Published: Wed Oct 22 2025 (10/22/2025, 08:27:04 UTC)
Source: CVE Database V5
Vendor/Project: beautifultemplates
Product: ST Categories Widget

Description

The ST Categories Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's st-categories shortcode in versions less than, or equal to, 1.0.0. This is due to insufficient input sanitization and output escaping on user supplied attributes. 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

AILast updated: 10/22/2025, 08:42:50 UTC

Technical Analysis

CVE-2025-11878 identifies a stored Cross-Site Scripting (XSS) vulnerability in the ST Categories Widget plugin for WordPress, specifically in versions less than or equal to 1.0.0. The root cause is insufficient sanitization and escaping of user-supplied attributes in the plugin's st-categories shortcode, which allows authenticated users with contributor-level permissions or higher to inject arbitrary JavaScript code into pages. This malicious code is stored persistently and executes in the browsers of any users who visit the infected pages, potentially leading to session hijacking, defacement, or unauthorized actions performed on behalf of users. The vulnerability requires authentication but no user interaction to trigger the script execution once the page is loaded. The CVSS 3.1 base score of 6.4 reflects a medium severity, with network attack vector, low attack complexity, and privileges required at the contributor level. The scope is changed, indicating that the vulnerability affects components beyond the initially vulnerable plugin, potentially impacting the broader WordPress environment. No public exploits have been reported yet, but the vulnerability is publicly disclosed and should be addressed promptly. The absence of a patch link suggests that a fix may not yet be available, emphasizing the need for interim mitigations. This vulnerability falls under CWE-79, which is a common and critical web application security issue related to improper neutralization of input during web page generation.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized script execution within their WordPress sites, compromising user session confidentiality and integrity. Attackers could steal cookies, perform actions on behalf of users, or inject malicious content that damages brand reputation. Organizations with contributor-level user roles broadly assigned increase the risk surface. Since WordPress powers a significant portion of European websites, especially in sectors like media, education, and small to medium enterprises, the impact could be widespread. The vulnerability does not affect availability directly but can lead to indirect denial of service through defacement or user distrust. Data privacy regulations such as GDPR heighten the consequences of such breaches, potentially resulting in regulatory penalties if personal data is compromised. The medium severity score indicates a moderate but actionable risk, particularly in environments where user roles are not tightly controlled or where the plugin is widely used.

Mitigation Recommendations

Immediate mitigation steps include restricting contributor-level access to trusted users only and auditing existing user roles to minimize unnecessary privileges. Site administrators should disable or remove the vulnerable ST Categories Widget plugin until a security patch is released. Implementing Web Application Firewalls (WAF) with rules targeting XSS payloads can provide temporary protection. Site owners should enforce strict Content Security Policies (CSP) to limit script execution sources. Regularly scanning WordPress installations for vulnerable plugins and monitoring for suspicious activity is critical. When a patch becomes available, prompt application is essential. Additionally, educating content contributors about safe input practices and limiting the use of shortcodes that accept user input can reduce exploitation risk. Backup strategies should be reviewed to ensure rapid recovery from potential compromise. Finally, monitoring public vulnerability databases and threat intelligence feeds for updates on exploits is recommended.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-10-16T17:38:43.762Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68f897b2d59611fbd9697949

Added to database: 10/22/2025, 8:37:06 AM

Last enriched: 10/22/2025, 8:42:50 AM

Last updated: 10/24/2025, 12:00:42 AM

Views: 16

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats