JiraApplication · Atlassian
CVE-2018-20232
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 labels widget gadget in Atlassian Jira before version 7.6.11 and from version 7.7.0 before version 7.13.1 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the rendering of retrieved content from a url location that could be manipulated by the up_projectid widget preference setting.
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 confidenceCross-site scripting (XSS) vulnerability in Atlassian Jira's labels widget gadget allows remote attackers to inject arbitrary HTML or JavaScript via manipulation of the up_projectid widget preference setting, which controls URL content retrieval and rendering.
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
< 7.6.11
Jira ServerApplication
>= 7.7.0, < 7.13.1CVSS 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.0/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 Jira versionCheck the Jira version by viewing the footer of any Jira page, or access /secure/AboutPage.jspa, or check the <Jira-installation>/atlassian-jira/WEB-INF/classes/jira-config.properties file if it existsAffected if The installed version is less than 7.6.11 OR is 7.7.0 through 7.13.0 (inclusive)
-
Locate labels widget gadget usageAccess Jira dashboards (navigate to a dashboard and edit) and look for the 'Labels' gadget or 'Labels Widget' gadget added to any dashboardAffected if The labels widget gadget is present on any dashboard in the environment
-
Inspect widget preference settingsWhile in dashboard edit mode, click the edit/configure option on the labels widget gadget and examine the 'Project ID' or 'up_projectid' preference settingAffected if The up_projectid preference is configured and contains user-supplied or untrusted content that could be manipulated
-
Check for existing XSS payloads in gadget configView the source HTML of a configured labels widget gadget page, or inspect the gadget's preferences via browser developer tools, looking for suspicious script tags or javascript: URIs in the up_projectid parameterAffected if Malicious JavaScript or HTML code is found within the up_projectid widget preference value
A user is affected if their Jira version falls within the vulnerable ranges AND the labels widget gadget with a configured up_projectid preference is in use on any dashboard.
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 data7.6.117.13.1
Upgrade Jira to version 7.6.11, 7.13.1, or later to patch the XSS vulnerability in the labels widget gadget.
Fix this in Jira
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20232 — 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-2018-20232 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