YoutrackApplication · Jetbrains

CVE-2025-57731

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 2025.2.92387 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
In JetBrains YouTrack before 2025.2.92387 stored XSS was possible via Mermaid diagram content

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 · high confidence

Stored cross-site scripting (XSS) vulnerability in JetBrains YouTrack allows attackers to inject malicious JavaScript code through Mermaid diagram content. The application fails to properly sanitize or encode Mermaid diagram text before rendering, enabling stored XSS that executes when other users view the diagram.

MitigationUpgrade YouTrack to version 2025.2.92387 or later. Until patched, restrict or carefully review Mermaid diagram content from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
YoutrackApplication
Affected:< 2025.2.92387

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify YouTrack version
    Navigate to Administration > Troubleshooting > System information in the YouTrack web interface, or check the build number in the bottom-left corner of any YouTrack page
    Affected if The installed version is less than 2025.2.92387 (the build number shown will be below 92387 in the 2025.2 release line)
  2. Confirm Mermaid diagram usage
    Search your YouTrack installation for any saved searches, issues, or wiki pages that contain Mermaid diagram syntax (look for code blocks or markdown fences labeled 'mermaid')
    Affected if Mermaid diagrams exist in the system and the YouTrack version is below 2025.2.92387
  3. Examine rendered Mermaid output
    Open an issue or page containing a Mermaid diagram, then use the browser developer tools (Inspect Element) to view the HTML source of the rendered diagram area
    Affected if The rendered diagram contains unsanitized HTML or executes JavaScript within the diagram rendering context

You are affected if YouTrack is running a version below 2025.2.92387 and Mermaid diagram content is being stored and rendered within the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2025.2.92387 or later
Fixed in 2025.2.92387
Interim mitigation

Upgrade YouTrack to version 2025.2.92387 or later. Until patched, restrict or carefully review Mermaid diagram content from untrusted sources.

Recommended fix High confidence

YouTrack 2025.2.92387

  1. Verify current YouTrack version by navigating to Administration > Global Settings > Application info
  2. Download YouTrack 2025.2.92387 or later from the official JetBrains website or your existing license download area
  3. Create a full backup of your YouTrack database and configuration files before upgrading
  4. Stop the YouTrack service or ensure no active users are connected during the upgrade
  5. Run the YouTrack installer or use the standard upgrade procedure for your deployment method (standalone or YouTrack InCloud)
  6. Start the YouTrack service after upgrade completes
  7. Verify the upgrade was successful by checking the version in Administration > Global Settings > Application info
  8. Test that Mermaid diagram functionality works properly and that stored XSS is no longer exploitable
Caveat Review JetBrains release notes for 2025.2.x for any configuration or feature changes that may affect your instance

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Youtrack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57731 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-57731 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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