YoutrackApplication · Jetbrains

CVE-2024-50582

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 2024.3.47707 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 2024.3.47707 stored XSS was possible due to improper HTML sanitization in markdown elements

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 XSS vulnerability in JetBrains YouTrack versions prior to 2024.3.47707 allowed attackers to inject malicious HTML/JavaScript through markdown elements due to improper HTML sanitization. When other users viewed the crafted markdown content, the injected scripts would execute in their browsers.

MitigationUpgrade YouTrack to version 2024.3.47707 or later which implements proper HTML sanitization for markdown rendering.

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

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 number
    Log into YouTrack as an administrator, navigate to Administration > System > Overview, and locate the 'YouTrack version' field. Alternatively, check the build number in the installation directory or startup logs.
    Affected if The installed version is less than 2024.3.47707 (for example, 2024.2.12345 or any version in the 2024.1.x, 2023.x, or earlier series).
  2. Confirm markdown feature is in use
    Verify that markdown formatting is enabled for issues, comments, or descriptions. Navigate to Administration > System > Markdown settings or review any issue that uses markdown syntax (such as **bold**, *italic*, [links](url), or code blocks).
    Affected if Markdown rendering is enabled, which is the default state in YouTrack.
  3. Review recent activity for suspicious content
    Search recent issues, comments, or descriptions for unusual HTML-like content or script tags. Use the YouTrack search to look for entries containing patterns like '<script', 'javascript:', 'onload=', or 'onerror='.
    Affected if Malicious markdown content containing injected HTML/JavaScript is present in any issue, comment, or description that other users have viewed.

You are affected if your YouTrack version is earlier than 2024.3.47707 and users can create or view markdown-formatted content in issues or comments.

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

Upgrade YouTrack to version 2024.3.47707 or later which implements proper HTML sanitization for markdown rendering.

Recommended fix High confidence

YouTrack 2024.3.47707 or later

  1. Back up your YouTrack database and configuration files before upgrading
  2. Stop the YouTrack service
  3. Download YouTrack version 2024.3.47707 or later from the official JetBrains website (www.jetbrains.com)
  4. Run the installer or apply the upgrade package to your existing installation
  5. Start the YouTrack service after the upgrade completes
  6. Verify that YouTrack is running correctly and test markdown rendering to confirm the XSS vulnerability is resolved
Caveat No specific breaking changes documented for this release; standard upgrade precautions apply (backup before upgrading)

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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