CVE-2025-23801
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 FuzzGuard Style Admin style-admin allows Stored XSS.This issue affects Style Admin: from n/a through <= 1.4.3.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in FuzzGuard Style Admin allows remote attackers to trick authenticated administrators into unknowingly submitting requests that inject malicious scripts, resulting in Stored XSS that executes for other admin users viewing the affected style content.
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.
-
Identify FuzzGuard installation and versionCheck the application for FuzzGuard presence by reviewing installed packages, application headers, or source code version files. Look for 'FuzzGuard' string in application metadata or admin interface.Affected if FuzzGuard is installed and the version cannot be confirmed to have anti-CSRF protection in Style Admin.
-
Confirm Style Admin component is accessibleNavigate to or enumerate the Style Admin interface within the FuzzGuard administrative panel. Verify the component exists and is reachable via web request.Affected if Style Admin component is present and accessible to authenticated administrators.
-
Verify anti-CSRF token implementation on Style Admin operationsInspect the HTTP requests and responses when creating/editing style content in Style Admin. Check if the form or API endpoints include anti-CSRF tokens in requests and if the server validates them.Affected if Style Admin state-changing operations (save/edit style) lack anti-CSRF token validation on the server side.
-
Check for Origin/Referer header validationSubmit a style content modification request with a mismatched or missing Origin/Referer header and observe if the server rejects the request.Affected if The server does not validate Origin or Referer headers for Style Admin operations, allowing cross-origin forged requests.
-
Inspect stored style content for malicious scriptsReview the database or style content storage for any injected script tags, event handlers (onerror, onload), or suspicious HTML in style fields that could execute when viewed by other admins.Affected if Style content contains persistent XSS payloads (script tags, event attributes) that execute when viewed by other administrators.
An administrator is affected if FuzzGuard Style Admin is in use, the Style Admin operations lack anti-CSRF token validation, and malicious script payloads have been stored in style content that executes for other admin users.
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 anti-CSRF tokens on all state-changing operations in the Style Admin component and validate Origin/Referer headers to prevent forged requests from injecting persistent XSS payloads.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23801 — 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-23801 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