Jenkins 360 FireLine Plugin vulnerable to XML External Entity Reference

published 2019-10-23 7y ago modified 2026-06-17 4mo ago also GHSA-346g-jrx9-jgf4 , EUVD-2022-2103

cvss: 8.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits: 0; none known

An XML external entities (XXE) vulnerability in Jenkins 360 FireLine Plugin allows attackers with Overall/Read access to have Jenkins resolve external entities, resulting in the extraction of secrets from the Jenkins agent, server-side request forgery, or denial-of-service attacks.

Is CVE-2019-10466 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:P/I:N/A:P
GitHub	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins.plugin:fireline	<=1.7.2	no fix listed

Affected products

Jenkins project Jenkins 360 FireLine Plugin

Classification

Weakness

CWE-611 Improper Restriction of XML External Entity Reference

References

jenkins.io /security/advisory/2019-10-23/#SECURITY-822
web, vendor-advisory
openwall.com /lists/oss-security/2019/10/23/2
mailing-list, web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2019-10466
advisory
github.com /jenkinsci/fireline-plugin
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.