CVE-2022-28650
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 2022.1.43700 it was possible to inject JavaScript into Markdown in the YouTrack Classic UI
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in JetBrains YouTrack Classic UI. An authenticated attacker can inject malicious JavaScript code into Markdown-formatted content. When other users view this content, the injected script executes in their browsers, potentially allowing session hijacking, data theft, or actions on behalf of victims.
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< 2022.1.43700CVSS 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 your YouTrack versionLog into YouTrack as an administrator and navigate to Administration > About, or check the version displayed in the footer of any YouTrack page. On self-hosted installations, you can also check the youtrack.jar file name or the installation logs.Affected if The version displayed is lower than 2022.1.43700
-
Confirm YouTrack Classic UI is enabledGo to Administration > Appearance > UI Style in YouTrack. Check whether the Classic UI option is selected or if the modern UI is the default. You can also inspect the URL pattern when browsing issues - Classic UI typically uses different URL paths.Affected if Classic UI is enabled or set as the default interface for users
-
Verify Markdown input is available to usersNavigate to a YouTrack project and create or edit an issue. Check if the Markdown editor is available in the description or comment fields. Test by adding simple Markdown text to see if it renders.Affected if Users can create or edit Markdown-formatted content in issues, comments, or descriptions
-
Check for untrusted or external user accessReview your user management in Administration > Users and Groups. Identify whether you have users who are not fully trusted, such as external guests, customers, or users with limited permissions who can submit content.Affected if There are users with write access to issues who are not fully trusted or are external to your organization
You are affected if your YouTrack version is below 2022.1.43700 AND Classic UI is enabled AND untrusted users can submit Markdown content in your YouTrack instance.
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 · scoped2022.1.43700
Upgrade YouTrack to version 2022.1.43700 or later. Until then, restrict Markdown input capabilities or disable YouTrack Classic UI for untrusted users.
2022.1.43700 or later
- Backup your YouTrack installation and database before upgrading
- Download YouTrack version 2022.1.43700 or a later stable release from the official JetBrains website (www.jetbrains.com/youtrack)
- Follow the standard YouTrack upgrade procedure for your deployment method
- Verify the upgrade was successful and the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28650 — 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-2022-28650 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