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/29/2025, 09:09:54 UTC

Technical Analysis

CVE-2025-11878 is a stored Cross-Site Scripting vulnerability identified in the ST Categories Widget plugin for WordPress, specifically affecting versions 1.0.0 and earlier. The vulnerability stems from insufficient sanitization and escaping of user-supplied attributes within the plugin's st-categories shortcode. Authenticated users with contributor-level access or higher can exploit this flaw by injecting arbitrary JavaScript code into pages or posts. Because the malicious script is stored persistently, it executes every time a user accesses the compromised page, potentially leading to session hijacking, credential theft, or unauthorized actions performed in the context of the victim's browser. The CVSS 3.1 base score is 6.4, reflecting a medium severity level, with an attack vector of network, low attack complexity, requiring privileges but no user interaction, and a scope change due to impact on other users. No public exploits have been reported yet, but the vulnerability poses a significant risk to websites that allow contributor-level users to add or edit content. The vulnerability affects all versions up to and including 1.0.0 of the plugin. The lack of patches at the time of reporting means that mitigation relies on access control and manual input validation until an official fix is released.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized script execution on their WordPress sites, compromising the confidentiality and integrity of user data. Attackers could steal session cookies, perform actions on behalf of users, or deliver further malware payloads. This is particularly concerning for organizations relying on WordPress for public-facing websites, intranets, or customer portals where contributor-level roles are assigned to multiple users. The impact extends to reputational damage, potential GDPR compliance violations due to data breaches, and operational disruptions if malicious scripts deface websites or redirect users. Since the vulnerability requires contributor-level authentication, insider threats or compromised accounts increase risk. The absence of known exploits reduces immediate threat but does not eliminate the risk of future attacks, especially as the vulnerability is publicly disclosed. Organizations with high web content management activity and multiple contributors are more vulnerable to exploitation.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations to identify the presence of the ST Categories Widget plugin and verify its version. Until an official patch is released, restrict contributor-level permissions to trusted users only and consider temporarily disabling the plugin if feasible. Implement Web Application Firewall (WAF) rules to detect and block suspicious shortcode attribute inputs that may contain script tags or event handlers. Conduct manual code reviews or use security plugins that enforce strict input validation and output encoding on shortcode attributes. Educate content contributors about the risks of injecting untrusted content and monitor logs for unusual activity indicative of exploitation attempts. Once a patch is available, prioritize timely updates. Additionally, consider deploying Content Security Policy (CSP) headers to limit the impact of any injected scripts. Regular backups and incident response plans should be updated to handle potential XSS incidents.

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/29/2025, 9:09:54 AM

Last updated: 12/5/2025, 3:53:01 PM

Views: 63

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