CVE-2024-50575
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 reflected XSS was possible in Widget API
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 confidenceReflected cross-site scripting (XSS) vulnerability in the Widget API of JetBrains YouTrack allows attackers to inject malicious scripts through unsanitized user inputs that are reflected back in server responses. This occurs in versions prior to 2024.3.47707.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed YouTrack versionAccess YouTrack admin area, go to Administration > System > Overview, or check the version displayed on the login page and in startup logsAffected if Version number is less than 2024.3.47707
-
Verify Widget API is accessibleCheck if the /api/widgets endpoint is reachable and not disabled in Administration > Settings > APIAffected if Widget API endpoints are exposed and accessible without additional restrictions
-
Check for unsanitized input reflectionSubmit a test request to a Widget API endpoint with a simple pattern like <script>alert(1)</script> in a parameter and inspect if it is reflected unchanged in the responseAffected if The submitted script tags or other HTML characters appear verbatim in the server response without encoding
You are affected if YouTrack version is below 2024.3.47707 AND the Widget API is enabled and accessible, allowing unsanitized user input to be reflected in responses.
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. If immediate upgrading is not possible, implement input validation and output encoding on the Widget API endpoints as a compensating control.
2024.3.47707 or later
- 1. Back up your YouTrack database and configuration files before starting the upgrade
- 2. Verify your current YouTrack version by navigating to Administration > Troubleshooting > System Info
- 3. Download YouTrack version 2024.3.47707 or later from the official JetBrains website (www.jetbrains.com/youtrack/download)
- 4. Follow JetBrains standard upgrade procedure: stop the YouTrack service, run the installer or deploy the new version, and start the service
- 5. After upgrade, navigate to Administration > Troubleshooting > System Info to confirm the version is 2024.3.47707 or higher
- 6. Test the Widget API functionality to ensure the reflected XSS fix is working properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50575 — 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-50575 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