CVE-2025-52792
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in vgstef WP User Stylesheet Switcher wp-user-stylesheet-switcher allows Stored XSS.This issue affects WP User Stylesheet Switcher: from n/a through <= v2.2.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCSRF vulnerability in WP User Stylesheet Switcher plugin up to v2.2.0 allows attackers to inject malicious JavaScript via Stored XSS by tricking authenticated administrators into clicking crafted links or visiting malicious pages that submit forged requests to the plugin's styling functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check plugin versionNavigate to WordPress admin > Plugins > Installed Plugins, locate 'WP User Stylesheet Switcher', and read the version number from the plugin description. Alternatively, inspect the main plugin file header in wp-content/plugins/wp-user-stylesheet-switcher/Affected if The installed version is 2.2.0 or any earlier version
-
Verify plugin is activeIn WordPress admin, confirm the plugin is both installed and activated. The vulnerability only affects active installations since inactive plugins do not process requests.Affected if The plugin is activated and processing requests
-
Inspect plugin forms for nonce validationExamine the plugin PHP files (particularly those handling form submissions or AJAX actions related to stylesheet switching) for the presence of wp_nonce_field() or check_admin_referer() calls. Search for forms that accept user-supplied CSS/styling data.Affected if Forms handling stylesheet data lack nonce verification (wp_nonce_field or check_admin_referer calls are missing)
-
Check stylesheet data handling for output encodingLocate code that retrieves and displays user-supplied stylesheet data (stored options, user meta, or database entries). Verify whether esc_html(), esc_attr(), or similar WordPress escaping functions are used before outputting the stylesheet content in admin pages or frontend.Affected if User-supplied stylesheet data is output without proper escaping functions like esc_html() or esc_attr()
You are affected if the installed plugin version is 2.2.0 or earlier AND the plugin is active AND the stylesheet switcher functionality lacks nonce validation on its forms and outputs user-supplied styling data without proper output encoding.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement WordPress nonces on all plugin forms and AJAX actions to validate request authenticity, and properly escape/output encoding when rendering user-supplied stylesheet data to prevent XSS execution.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52792 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data