EUVD-2025-28467CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Lifecycle Timeline
3Description
Cross-Site Request Forgery (CSRF) vulnerability in vgstef WP User Stylesheet Switcher allows Stored XSS. This issue affects WP User Stylesheet Switcher: from n/a through v2.2.0.
Analysis
CVE-2025-52792 is a Cross-Site Request Forgery (CSRF) vulnerability in the vgstef WP User Stylesheet Switcher WordPress plugin (versions up to v2.2.0) that enables Stored XSS attacks. An unauthenticated attacker can exploit this via a simple network request with user interaction to inject malicious scripts that execute in victims' browsers, potentially compromising user sessions and data. The vulnerability has not been confirmed as actively exploited in the wild, though the high CVSS score (7.1) and network-accessible attack vector indicate practical exploitability.
Technical Context
WP User Stylesheet Switcher is a WordPress plugin that allows users to switch between different stylesheets. The vulnerability stems from inadequate CSRF token validation (CWE-352: Cross-Site Request Forgery) combined with insufficient input sanitization that permits Stored XSS injection. The plugin fails to properly implement WordPress's nonce verification mechanisms, allowing attackers to craft malicious requests that modify plugin settings or user data without explicit authorization. The stored nature of the XSS means the payload persists in the database and executes whenever affected pages are rendered, affecting all users who interact with compromised content. The CPE identifier would be: cpe:2.7:a:vgstef:wp_user_stylesheet_switcher:*:*:*:*:*:wordpress:*:* (versions through 2.2.0).
Affected Products
WP User Stylesheet Switcher (All versions from initial release through v2.2.0)
Remediation
Navigate to WordPress admin > Plugins > Installed Plugins, locate WP User Stylesheet Switcher, and click Update if available Mitigation (if patch unavailable): WordPress admin > Plugins > Installed Plugins > Deactivate WP User Stylesheet Switcher Defense in Depth: Use security plugins (e.g., Wordfence, Sucuri) to monitor for exploitation attempts and enforce nonce validation site-wide Monitoring: Review WordPress user activity logs and plugin settings for anomalies post-disclosure
Priority Score
Share
External POC / Exploit Code
Leaving vuln.today