# CVE-2021-21672: XXE vulnerability in Jenkins Selenium HTML report Plugin

> An attacker can exploit XML external entity vulnerabilities in the Jenkins Selenium HTML report plugin to read sensitive files or cause denial of service.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hxxp-6546-wv6r

## What is CVE-2021-21672?

CVE-2021-21672 is a medium-severity vulnerability in Jenkins Selenium HTML report Plugin, published on 30 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Selenium HTML report Plugin 1.0 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

2 open source packages ship an affected version, including org.jenkins-ci.plugins:seleniumhtmlreport. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:seleniumhtmlreport` | Maven | All versions | 1.1 |
| `org.jenkins-ci.plugins:seleniumhtmlreport` | Maven | All versions | 1.1 |

Products: Jenkins Selenium Html Report.

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

Upgrade org.jenkins-ci.plugins:seleniumhtmlreport to 1.1 or later.

## Is CVE-2021-21672 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-21672 is a medium-severity vulnerability in Jenkins Selenium HTML report Plugin, published on 30 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-21672 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:seleniumhtmlreport (Maven): affected all versions; fixed in 1.1
- org.jenkins-ci.plugins:seleniumhtmlreport (Maven): affected all versions; fixed in 1.1

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

## Sources

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

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