CVE-2024-50576
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 · uneditedIn JetBrains YouTrack before 2024.3.47707 stored XSS was possible via vendor URL in App manifest
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 confidenceA stored cross-site scripting (XSS) vulnerability in JetBrains YouTrack versions prior to 2024.3.47707 allows attackers to inject malicious JavaScript code through the vendor URL field in an App manifest. Since this is a stored XSS, the payload persists on the server and executes when other users interact with the affected manifest data.
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< 2024.3.47707CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed YouTrack versionNavigate to YouTrack administration > About page (typically at /admin/about) or check the installation directory for version information. Compare the version number to the affected range: versions prior to 2024.3.47707 are vulnerable.Affected if The installed version is less than 2024.3.47707.
-
Determine if App manifests are in useCheck if your YouTrack instance has any custom apps or integrations installed that use the App manifest functionality. Look in Administration > Apps or the apps directory in your installation.Affected if Apps with manifests are created or imported into the YouTrack instance.
-
Inspect vendor URL fields in existing App manifestsAccess any installed App manifests and examine the vendor URL field. This is typically found in the manifest configuration or app metadata. Look for any URLs containing HTML tags, JavaScript code, or unusual characters that may indicate a stored XSS payload.Affected if The vendor URL field contains unsanitized HTML, JavaScript code, or suspicious characters that could execute as script.
-
Review recent manifest modificationsCheck YouTrack audit logs or version history for recent changes to App manifests, particularly the vendor URL field. Look for unexpected or suspicious modifications.Affected if There are unauthorized or unexpected changes to vendor URL fields in App manifests.
You are affected if your YouTrack version is earlier than 2024.3.47707 AND you have App manifests with a vendor URL field that contains unsanitized or malicious content.
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.
dbcve · scoped2024.3.47707
Upgrade YouTrack to version 2024.3.47707 or later. Apply the latest security patches and verify the vendor URL input validation is properly sanitized in the App manifest functionality.
2024.3.47707 or later
- 1. Back up your YouTrack database and configuration before upgrading
- 2. Download YouTrack version 2024.3.47707 or later from the official JetBrains website (www.jetbrains.com/youtrack/download)
- 3. Follow the standard YouTrack upgrade instructions for your installation method
- 4. Verify the upgrade was successful by checking the YouTrack version in Administration > Application section
- 5. Test that the vendor URL field in App manifests now properly sanitizes input to prevent XSS
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50576 — 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-2024-50576 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