JiraApplication · Atlassian
CVE-2018-5230
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 issue collector in Atlassian Jira before version 7.6.6, from version 7.7.0 before version 7.7.4, from version 7.8.0 before version 7.8.4 and from version 7.9.0 before version 7.9.2 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the error message of custom fields when an invalid value is specified.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in Atlassian Jira's issue collector component. When custom fields receive invalid values, the error message is not properly sanitized, allowing remote attackers to inject arbitrary HTML or JavaScript that executes in the browsers of users viewing these error messages.
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.6
Jira ServerApplication
>= 7.7.0, < 7.7.4>= 7.8.0, < 7.8.4>= 7.9.0, < 7.9.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.
-
Determine your Jira installation versionLog in as an administrator and navigate to Administration > System > System Info, or access the /rest/api/2/serverInfo endpoint to retrieve the installed Jira version.Affected if The displayed version falls within any of these ranges: < 7.6.6, OR >= 7.7.0 and < 7.7.4, OR >= 7.8.0 and < 7.8.4, OR >= 7.9.0 and < 7.9.2.
-
Verify whether issue collectors are configuredNavigate to Administration > Issues > Issue Collectors (or check for issue collector plugins/web-sections) to see if any issue collectors have been created in your Jira instance.Affected if Any issue collector is active and users can submit issues through it.
-
Identify custom fields that may be used in issue collectorsReview your issue collector configurations to determine which custom fields are included in the submission forms, particularly any custom fields that might accept user input and could trigger validation errors.Affected if Issue collectors include custom fields that perform validation and could generate error messages.
Your environment is affected if your Jira version is below 7.6.6, between 7.7.0-7.7.3, between 7.8.0-7.8.3, or between 7.9.0-7.9.1, AND you have active issue collectors with custom fields that validate input.
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.67.7.47.8.4
Upgrade Jira to version 7.6.6, 7.7.4, 7.8.4, 7.9.2 or later to patch the XSS vulnerability in the issue collector's error message handling.
Fix this in Jira
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5230 — 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-5230 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