dbcve.org
YoutrackApplication · Jetbrains

CVE-2024-49579

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-17
Fix available
A fix is available. Upgrade to 2024.3.47197 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.47197 insecure plugin iframe allowed arbitrary JavaScript execution and unauthorized API requests

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 confidence

Insecure plugin iframe in JetBrains YouTrack before version 2024.3.47197 allowed arbitrary JavaScript execution in the context of the YouTrack application, enabling attackers to perform unauthorized API requests. This is a Cross-Site Scripting (XSS) vulnerability in YouTrack's plugin system where iframe content is not properly validated.

MitigationUpgrade YouTrack to version 2024.3.47197 or later to remediate the insecure plugin iframe vulnerability.

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.47197

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
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed YouTrack version
    Log into YouTrack as an administrator and navigate to Administration > About, or check the <youtrack_installation>/conf/youtrack.properties file for the build number
    Affected if The version shown is less than 2024.3.47197
  2. Verify plugin iframe usage
    Navigate to Administration > Plugins and review the list of installed plugins. Look for any plugins that utilize iframe functionality or external content embedding
    Affected if Any third-party or custom plugins with iframe components are installed and enabled
  3. Inspect plugin configuration for iframe sources
    Examine each plugin's settings that includes iframe or web-frame components. Check the source URLs configured in these iframe settings for unexpected or malicious domains
    Affected if Plugin iframe sources point to untrusted or unfamiliar domains, or contain suspicious URL patterns
  4. Review browser console for XSS indicators
    Open the browser developer console while browsing YouTrack. Look for any console errors related to Content Security Policy violations, or unexpected script executions that may indicate exploitation attempts
    Affected if CSP violations or unexpected script errors appear in the console

A user is affected if their YouTrack installation version is below 2024.3.47197 and they have plugins with iframe functionality enabled.

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.47197 or later
Fixed in 2024.3.47197
Interim mitigation

Upgrade YouTrack to version 2024.3.47197 or later to remediate the insecure plugin iframe vulnerability.

Recommended fix High confidence

YouTrack 2024.3.47197 or later

  1. Back up your YouTrack data and configuration before upgrading
  2. Stop the YouTrack service
  3. Download YouTrack version 2024.3.47197 or later from the official JetBrains website (www.jetbrains.com/youtrack)
  4. Install the upgrade following JetBrains standard upgrade procedures for your deployment type (standalone or YouTrack InCloud)
  5. Start the YouTrack service after upgrade completes
  6. Verify the upgrade was successful by checking the YouTrack version in Administration > System > Overview

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49579 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-49579 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