# CVE-2018-5230: Cross-site scripting in Jira

> Remote attackers can inject arbitrary HTML or JavaScript via XSS in Jira's issue collector error messages, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7cw6-37m4-4r8g

## What is CVE-2018-5230?

CVE-2018-5230 is a medium-severity cross-site scripting vulnerability in Atlassian Jira, published on 14 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-5230?

It affects 2 products.


Products: Atlassian Jira, Atlassian Jira Server.

## How do I fix CVE-2018-5230?

No fix has been published for CVE-2018-5230 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-5230 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-5230 exists.

Public exploit code:

- Atlassian Jira Confluence - Cross-Site Scripting (nuclei): http/cves/2018/CVE-2018-5230.yaml

## Other vulnerabilities in Atlassian Jira

- [CVE-2020-14172](https://insights.sbomify.com/CVE-2020-14172/): Deserialization in Jira Server (critical 9.8)
- [CVE-2019-20409](https://insights.sbomify.com/CVE-2019-20409/): Code injection in Jira Server (critical 9.8)
- [CVE-2017-5983](https://insights.sbomify.com/CVE-2017-5983/): Deserialization in n/a (critical 9.8)
- [CVE-2010-1165](https://insights.sbomify.com/CVE-2010-1165/): Code injection in n/a (critical 9.0)
- [CVE-2016-4319](https://insights.sbomify.com/CVE-2016-4319/): Cross-site request forgery in Atlassian JIRA Server before 7.1.9 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5230 and fix it if it is affected.

What it is: CVE-2018-5230 is a medium-severity cross-site scripting vulnerability in Atlassian Jira, published on 14 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-5230 exists.

Affected product: Atlassian Jira. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-5230/ (Markdown: https://insights.sbomify.com/CVE-2018-5230/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-5230
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-5230
- OSV: https://osv.dev/vulnerability/CVE-2018-5230

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-5230/
Summaries are generated and may contain mistakes; the official description above is the record.