# CVE-2021-39111: Cross-site scripting in Jira Data Center

> Remote attackers can inject arbitrary HTML or JavaScript via XSS in the Editor plugin when pasting content, potentially leading to code execution or account takeover.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** 30 Aug 2021
- **Updated:** 11 Oct 2024
- **Also known as:** GHSA-56cm-gqqx-cjww

## What is CVE-2021-39111?

CVE-2021-39111 is a medium-severity cross-site scripting vulnerability in Atlassian Jira, published on 30 Aug 2021. 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 Editor plugin in Atlassian Jira Server and Data Center before version 8.5.18, from 8.6.0 before 8.13.10, and from version 8.14.0 before 8.18.2 allows remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability in the handling of supplied content such as from a PDF when pasted into a field such as the description field.

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

## Which versions are affected by CVE-2021-39111?

It affects 4 products.


Products: Atlassian Data Center, Atlassian Jira, Atlassian Jira Data Center, Atlassian Jira Server.

## How do I fix CVE-2021-39111?

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

## Is CVE-2021-39111 being exploited?

There is no known exploitation of CVE-2021-39111 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Jira

- [CVE-2017-18113](https://insights.sbomify.com/CVE-2017-18113/): Code injection in Jira Data Center (high 8.8)
- [CVE-2021-41312](https://insights.sbomify.com/CVE-2021-41312/): Auth bypass in Jira Data Center (high 7.5)
- [CVE-2021-39123](https://insights.sbomify.com/CVE-2021-39123/): Denial of service in Jira Data Center (high 7.5)
- [CVE-2021-39113](https://insights.sbomify.com/CVE-2021-39113/): Missing authorization in Jira Data Center (high 7.5)
- [CVE-2021-43947](https://insights.sbomify.com/CVE-2021-43947/): Code injection in Jira Data Center (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-39111 and fix it if it is affected.

What it is: CVE-2021-39111 is a medium-severity cross-site scripting vulnerability in Atlassian Jira, published on 30 Aug 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-39111 in the wild and no public exploit code.

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-2021-39111/ (Markdown: https://insights.sbomify.com/CVE-2021-39111/index.md)
```

## Sources

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

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