CVE-2022-28648
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.43563 HTML code from the issue description was being rendered
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 Cross-Site Scripting (XSS) vulnerability in JetBrains YouTrack where HTML code from issue descriptions was being rendered without proper sanitization, allowing attackers to inject malicious scripts that would execute in the browsers of users viewing those issues.
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.43563CVSS 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.
-
Check YouTrack versionLog into YouTrack as administrator, go to Administration > System > Overview, and locate the 'YouTrack version' field. Alternatively, check the build number in the footer of any YouTrack page or in the installation directory if self-hosted.Affected if The displayed version is any build earlier than 2022.1.43563 (for example, 2022.1.40000, 2021.x series, or earlier)
-
Confirm YouTrack is accessible to usersVerify that users have the ability to create or edit issues. This is a core YouTrack functionality and is typically enabled by default for most user roles.Affected if Users can create or modify issue descriptions, as this is the feature where unsanitized HTML gets rendered
You are affected if your YouTrack build number is below 2022.1.43563 and users can create or view issue descriptions in your installation.
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.43563
Upgrade YouTrack to version 2022.1.43563 or later, which includes proper HTML sanitization for issue descriptions.
YouTrack 2022.1.43563 or later
- Back up your YouTrack database and configuration files before starting the upgrade
- Stop the YouTrack service
- Download YouTrack version 2022.1.43563 or later from the official JetBrains website (www.jetbrains.com/youtrack/download)
- Follow JetBrains installation/upgrade instructions for your deployment type (standalone or InCloud)
- Start the YouTrack service
- Verify that YouTrack is running the fixed version by checking the build number in Administration > Application section
- Test that issue descriptions no longer execute raw HTML/JavaScript code
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28648 — 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-28648 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