CVE-2025-31391
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 regen Script Compressor script-compressor allows Stored XSS.This issue affects Script Compressor: from n/a through <= 1.7.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 Script Compressor allows attackers to craft malicious requests that result in Stored XSS, enabling persistent script injection against users who access the affected 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.
-
Identify Script Compressor installationLocate the Script Compressor module or component within your application codebase. Search for files or modules named 'ScriptCompressor', 'script-compressor', or similar naming patterns related to script compression functionality.Affected if Script Compressor is present in your environment and handles user-supplied script content without proper validation.
-
Verify CSRF protection existsInspect the request handling code for the Script Compressor functionality. Look for the presence of anti-CSRF tokens, SameSite cookie attributes, or CSRF token validation logic in state-changing operations.Affected if State-changing operations in the Script Compressor lack CSRF token validation or SameSite cookie protections.
-
Check input validation on script contentReview the code that processes script input sent to the Script Compressor. Examine how user-supplied scripts are received, stored, and later served to other users.Affected if User-supplied script content is stored without sanitization or output encoding, allowing persistent injection.
-
Test for stored XSS via Script CompressorIf you have access to a testing environment, submit a script payload containing a benign test string (such as <script>alert('test')</script>) through the Script Compressor feature. Then access the compressed output as another user would.Affected if The submitted script content is rendered in the browser without encoding when other users access the compressed script output.
Your environment is affected if the Script Compressor feature is enabled and processes user-supplied script content without CSRF protection and output encoding, allowing stored XSS injection.
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 for state-changing operations and apply output encoding/validation to prevent stored XSS injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31391 — 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-31391 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