YoutrackApplication · Jetbrains

CVE-2023-35054

MEDIUM · 5.4 CVSS v3.1 Published 2023-06-12
Fix available
A fix is available. Upgrade to 2023.1.10518 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 2023.1.10518 stored XSS in a Markdown-rendering engine was possible

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

A stored Cross-Site Scripting (XSS) vulnerability exists in JetBrains YouTrack's Markdown rendering engine in versions prior to 2023.1.10518. An attacker can embed malicious JavaScript code within Markdown content that gets stored on the server and executed when other users view the rendered content.

MitigationUpgrade YouTrack to version 2023.1.10518 or later. Review existing Markdown content in the system for any previously injected malicious scripts.

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:< 2023.1.10518

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. Check YouTrack version
    Log into YouTrack as an administrator and navigate to Administration > System > Overview, or use the command: {base-url}/api/admin/systemInfo. The version is displayed in the 'YouTrack version' field.
    Affected if The installed version is lower than 2023.1.10518 (e.g., 2023.1.x versions before 10518, or any version in the 2022.x, 2021.x series).
  2. Identify Markdown usage
    Review which projects and issue fields use the Markdown renderer. Check project settings under Projects > [Project Name] > Field Settings, looking for fields with 'Markdown' or 'Text (Markdown)' type.
    Affected if Markdown fields are in use and visible to multiple users, allowing stored XSS to propagate.
  3. Inspect stored Markdown content
    Query the database or export issues to identify Markdown fields containing HTML script tags, javascript: URIs, or event handlers (onclick, onerror, onload). Check the 'description' and 'comment' fields specifically.
    Affected if Malicious script tags or JavaScript event handlers are found embedded in Markdown content that was authored by another user.
  4. Review audit and server logs
    Examine YouTrack audit logs (Administration > System > Audit Log) and the service logs for entries containing Markdown submissions that include unusual characters or patterns typical of XSS payloads.
    Affected if Logs show Markdown content submissions containing <script>, javascript:, or HTML event handler attributes.

You are affected if your YouTrack installation is version 2023.1.10518 or earlier and users can create or view Markdown-rendered content from other users.

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 2023.1.10518 or later
Fixed in 2023.1.10518
Interim mitigation

Upgrade YouTrack to version 2023.1.10518 or later. Review existing Markdown content in the system for any previously injected malicious scripts.

Recommended fix Moderate confidence

2023.1.10518 or later (2023.1.x branch)

  1. Back up your YouTrack database and installation directory before upgrading
  2. Download YouTrack 2023.1.10518 or later from the official JetBrains website (www.jetbrains.com)
  3. Stop the YouTrack service
  4. Extract the new version to your installation directory
  5. Start the YouTrack service and verify the upgrade was successful
Caveat Review JetBrains release notes for any breaking changes between your current version and 2023.1.10518; consider testing in a staging environment first

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35054 — 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-2023-35054 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