# CVE-2019-20903: Cross-site scripting in @atlaskit/editor-core

> Remote attackers can inject arbitrary HTML or JavaScript via link targets in the Atlassian editor library, potentially executing code in user sessions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Oct 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-p5ch-w78f-xh44

## What is CVE-2019-20903?

CVE-2019-20903 is a medium-severity cross-site scripting vulnerability in Atlassian @atlaskit/editor-core, published on 1 Oct 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The hyperlinks functionality in atlaskit/editor-core in before version 113.1.5 allows remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability in link targets.

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

## Which versions are affected by CVE-2019-20903?

2 open source packages ship an affected version, including @atlaskit/editor-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@atlaskit/editor-core` | npm | All versions | None |
| `@atlaskit/editor-core` | npm | All versions | None |

Products: Atlassian Editor-Core.

## How do I fix CVE-2019-20903?

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

## Is CVE-2019-20903 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20903 and fix it if it is affected.

What it is: CVE-2019-20903 is a medium-severity cross-site scripting vulnerability in Atlassian @atlaskit/editor-core, published on 1 Oct 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-20903 in the wild and no public exploit code.

Affected packages and fixed versions:
- @atlaskit/editor-core (npm): affected all versions; no fix listed
- @atlaskit/editor-core (npm): affected all versions; no fix listed

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

## Sources

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

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