CVE-2025-60172
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 flytedesk Flytedesk Digital flytedesk-digital allows Stored XSS.This issue affects Flytedesk Digital: from n/a through <= 20181101.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in Flytedesk Digital enables Stored XSS attacks. Attackers can exploit the lack of CSRF protection to trick authenticated users into performing unintended actions that inject malicious scripts into the application, which are then stored and executed when other users view the affected content. The vulnerability exists in all versions through 20181101.
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 Flytedesk Digital versionLocate the application version number in the software itself, typically found in the admin panel under 'About' or 'System Information', or check the installation files for a version manifestAffected if The installed version is 20181101 or earlier (date-based version numbering)
-
Check for CSRF token presence in state-changing formsInspect the HTML source of forms that perform actions (submit buttons, data entry forms) to verify each includes a hidden CSRF token fieldAffected if Forms lack hidden CSRF token fields and do not validate Origin or Referer headers
-
Verify SameSite cookie attribute configurationExamine the session cookie settings in the application or proxy configuration to determine if SameSite attribute is set to 'Strict' or 'Lax'Affected if Cookies do not have SameSite attribute configured or it is set to 'None' without Secure flag
-
Test for stored XSS via form submissionSubmit a test script tag payload (e.g., <script>alert(1)</script>) through user-controllable input fields and verify if it executes when the data is displayed backAffected if The payload is rendered unescaped in the application interface, indicating lack of output encoding
The environment is affected if Flytedesk Digital version is 20181101 or earlier, forms lack CSRF protections, and user inputs are not properly sanitized allowing stored XSS execution.
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 and Referer headers, and apply SameSite cookie attributes to prevent cross-site request forgery. Additionally, implement proper input validation and output encoding to prevent stored XSS.
- 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-60172 — 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-60172 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