How severe is CVE-2019-10475?

CVE-2019-10475 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-10475?

CVE-2019-10475 affects the following packages: org.jenkins-ci.plugins:build-metrics (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-10475?

No fixed version has been published for CVE-2019-10475 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2019-10475 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2019-10475, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-10475?

CVE-2019-10475 has an EPSS (Exploit Prediction Scoring System) score of 92.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for CVE-2019-10475?

A Nuclei detection template exists for CVE-2019-10475, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-10475 published, and has it been updated?

CVE-2019-10475 was published on October 23, 2019 and was last updated on March 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2019-10475

MEDIUM

Jenkins build-metrics Plugin reflected cross-site scripting vulnerability

Also known asGHSA-f8w9-66fp-3jgw

Published

Oct 23, 2019

Updated

Mar 15, 2026

Affected

1 pkg

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

92.4%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.jenkins-ci.plugins:build-metrics

Real-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

A reflected cross-site scripting vulnerability in Jenkins build-metrics Plugin allows attackers to inject arbitrary HTML and JavaScript into web pages provided by this plugin.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:build-metrics`	all versions	No fix

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-47598webappsjava

Jenkins build-metrics plugin 1.3 - 'label' Cross-Site Scripting

by vesche · Nov 8, 2019

Exploit-DB Source

Frequently Asked Questions

A reflected cross-site scripting vulnerability in Jenkins build-metrics Plugin allows attackers to inject arbitrary HTML and JavaScript into web pages provided by this plugin.

O3 Security · Impact-Aware SCA

Is CVE-2019-10475 in your stack?

O3 detects CVE-2019-10475 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works