JiraApplication · Atlassian
CVE-2019-11584
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 · uneditedThe MigratePriorityScheme resource in Jira before version 8.3.2 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the priority icon url of an issue priority.
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 Atlassian Jira before version 8.3.2. The MigratePriorityScheme resource fails to properly sanitize the priority icon URL field when creating or modifying issue priorities, allowing remote attackers to inject malicious HTML or JavaScript that executes in the browsers of other users who view the affected priority.
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
JiraApplication
< 8.3.2CVSS 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.0/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.
-
Check Jira versionNavigate to Jira Administration > System > System Info or access /rest/api/2/serverInfo to retrieve the installed Jira version numberAffected if The installed version is lower than 8.3.2 (e.g., 8.3.1, 8.2.x, 8.1.x, etc.)
-
Verify access to MigratePrioritySchemeAttempt to access the MigratePriorityScheme resource endpoint or navigate to Administration > Issues > Priorities to view priority configurationAffected if User has administrative privileges to modify priority settings and the MigratePriorityScheme functionality is enabled and accessible
-
Inspect priority icon URLsReview existing priorities at Administration > Issues > Priorities and check the Icon URL field for each priority; verify if any URLs contain unsanitized or suspicious contentAffected if Any priority has an Icon URL field containing HTML, JavaScript, or unusual characters that were not properly escaped (e.g., <script>, javascript:, onerror=)
A user is affected if their Jira installation is version 8.3.2 or later AND no priorities contain malicious XSS payloads in the Icon URL field, otherwise they are vulnerable if running a version below 8.3.2 with accessible priority modification features.
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.
From vendor data8.3.2
Upgrade Jira to version 8.3.2 or later to remediate this vulnerability. If immediate upgrading is not feasible, restrict administrative access to the MigratePriorityScheme functionality and implement strict Content Security Policy headers as a defensive measure.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11584 — 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-2019-11584 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