Skip to content
Fencer Vulns
medium 5.4

CVE-2021-21619 json

XSS vulnerability in Jenkins Claim Plugin

published 2021-02-24 5 y ago modified 2026-06-17 4 mo ago also GHSA-48hr-jg4p-w4p4 , EUVD-2022-2338

cvss
5.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.4%
EPSS 9.4% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Jenkins Claim Plugin 2.18.1 and earlier does not escape the user display name, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers who are able to control the display names of Jenkins users, either via the security realm, or directly inside Jenkins.

Patch / fix

  • maven org.jenkins-ci.plugins:claim 2.18.2

Exploit prediction

9.39% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:claim
<2.18.2
2.18.2

Affected products

  • Jenkins project Jenkins Claim Plugin

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns 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.