Technical impact
The vulnerability arises from Jenkins deserializing XML configuration files without enforcing item type restrictions, permitting attackers who can reach the POST config.xml API endpoints to submit crafted XML that can inject malicious content. When a malicious config.xml containing executable scripts is processed, it can result in stored cross‑site scripting, allowing attackers to run arbitrary client‑side code whenever users view affected jobs or dashboards. This weakness primarily concerns the integrity and confidentiality of user sessions and can be leveraged for phishing or credential theft, but does not directly affect data confidentiality or system availability.
Affected Systems
Jenkins Project’s Jenkins CI server is affected, specifically installations running version 2.587 or earlier, as well as the LTS release 2.580.1 and earlier. Systems that have not applied these newer releases remain vulnerable if attackers can submit job configuration files via the web API.
Risk and Exploitability
The flaw is exploitable through the RESTful POST config.xml API; based on the description, it is inferred that an attacker must have network access to the Jenkins controller and some level of job‑configuration authority. With a CVSS score of 5.4, the vulnerability is considered moderate, and its EPSS score of <1% suggests a low probability of exploitation at this time. Although the vulnerability is not listed in the CISA KEV catalog, the nature of stored XSS is widely recognized as high‑impact, especially in environments where users routinely view job pages. Fixing the issue by upgrading Jenkins or tightening API permissions mitigates the exposure.