CVE-2021-21672 is a medium-severity (CVSS 4.3) XML External Entity (XXE) vulnerability in org.jenkins-ci.plugins:seleniumhtmlreport. EPSS puts its 30-day exploitation probability at 42.5% (99th percentile). A fix is available for org.jenkins-ci.plugins:seleniumhtmlreport — see the affected versions and patch details below.
XXE vulnerability in Jenkins Selenium HTML report Plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-21672 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.jenkins-ci.plugins:seleniumhtmlreportReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins Selenium HTML report Plugin 1.0 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
This allows attackers with the ability to control the report files parsed using this plugin to have Jenkins parse a crafted report file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.
Jenkins Selenium HTML report Plugin 1.1 disables external entity resolution for its XML parser.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:seleniumhtmlreport | all versions | 1.1org.jenkins-ci.plugins:seleniumhtmlreport:1.1 |
Affected Products
selenium html reportjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:seleniumhtmlreport, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:seleniumhtmlreport to 1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21672 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2021-21672 in your dependencies?
Find it across Maven, including transitive dependencies.