# CVE-2020-1933: Cross-site scripting in Apache NiFi

> An attacker can inject malicious scripts into the Apache NiFi UI via an authenticated user in Firefox, 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:** Yes
- **Published:** 28 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-nifi-2020-1933, GHSA-pqhq-xx62-2v2p

## What is CVE-2020-1933?

CVE-2020-1933 is a medium-severity cross-site scripting vulnerability in Apache Nifi, published on 28 Jan 2020. 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

A XSS vulnerability was found in Apache NiFi 1.0.0 to 1.10.0. Malicious scripts could be injected to the UI through action by an unaware authenticated user in Firefox. Did not appear to occur in other browsers.

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

## Which versions are affected by CVE-2020-1933?

3 open source packages ship an affected version, including org.apache.nifi:nifi and nifi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.nifi:nifi` | Maven | From 1.0.0 | 1.11.0 |
| `org.apache.nifi:nifi` | Maven | From 1.0.0 | 1.11.0 |
| `nifi` | Bitnami | From 1.0.0 to 1.10.0 | None |

Products: Apache Nifi.

## How do I fix CVE-2020-1933?

Upgrade org.apache.nifi:nifi to 1.11.0 or later.

## Is CVE-2020-1933 being exploited?

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

## Other vulnerabilities in Apache Nifi

- [CVE-2018-1309](https://insights.sbomify.com/CVE-2018-1309/): Improper Restriction of XML External Entity Reference in Apache NiFi (critical 9.8)
- [CVE-2017-15697](https://insights.sbomify.com/CVE-2017-15697/): Apache NiFi XSS issue in context path handling (critical 9.8)
- [CVE-2017-5636](https://insights.sbomify.com/CVE-2017-5636/): Injection in Apache NiFi (critical 9.8)
- [CVE-2026-68981](https://insights.sbomify.com/CVE-2026-68981/): Apache NiFi: Uncontrolled Resource Consumption through Decompression of HTTP Requests (high 8.8)
- [CVE-2023-36542](https://insights.sbomify.com/CVE-2023-36542/): Apache NiFi: Potential Code Injection with Properties Referencing Remote Resources (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1933 and fix it if it is affected.

What it is: CVE-2020-1933 is a medium-severity cross-site scripting vulnerability in Apache Nifi, published on 28 Jan 2020. 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-2020-1933 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.nifi:nifi (Maven): affected from 1.0.0; fixed in 1.11.0
- org.apache.nifi:nifi (Maven): affected from 1.0.0; fixed in 1.11.0
- nifi (Bitnami): affected from 1.0.0 up to 1.10.0; 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-2020-1933/ (Markdown: https://insights.sbomify.com/CVE-2020-1933/index.md)
```

## Sources

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

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