CVE-2025-23976
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 operationsissuu Issuu Panel issuu-panel allows Stored XSS.This issue affects Issuu Panel: from n/a through <= 2.1.1.
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 Issuu Panel allows authenticated attackers to craft malicious requests that inject and persist XSS payloads in the application. When other users access the affected content, the stored JavaScript executes in their browsers, enabling session hijacking, credential theft, or defacement.
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 Issuu Panel installationCheck the application name/version by reviewing the web application banner, about page, or HTTP headers for 'Issuu Panel' referencesAffected if The application is not Issuu Panel (this CVE does not apply)
-
Verify anti-CSRF token presenceInspect HTML forms and AJAX requests for hidden CSRF token fields. Submit a state-changing request (e.g., profile update, content creation) without a token and observe if the request is acceptedAffected if State-changing operations lack anti-CSRF tokens or tokens are not validated server-side
-
Check SameSite cookie attributesExamine session cookies using browser dev tools or by inspecting Set-Cookie headers. Verify if the SameSite attribute is set to 'Strict' or 'Lax'Affected if Session cookies lack SameSite attribute or have it set to 'None' without Secure flag
-
Inspect Origin/Referer header validationSend a crafted request with missing or mismatched Origin/Referer headers using a tool like Burp Suite or curl. Observe if the server accepts the requestAffected if Server accepts requests without validating Origin or Referer headers
-
Test for stored XSS injectionCreate or modify content in the Issuu Panel (e.g., profile, document metadata) with a benign test payload like <script>alert(1)</script> or <img src=x onerror=alert(1)>. Access the content from a different session to confirm persistenceAffected if The XSS payload executes in another user's browser without sanitization
A user is affected if they run Issuu Panel and the application lacks anti-CSRF tokens, proper SameSite cookie settings, and Origin/Referer validation, allowing stored XSS to persist and execute for other 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, validate Origin/Referer headers server-side, and set SameSite attributes on session cookies to prevent cross-site request forgery.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23976 — 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-23976 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