Jenkins Project Jenkins Git Parameter Plugin vulnerabilities

6 vulnerabilities

Known vulnerabilities in Jenkins Project Jenkins Git Parameter Plugin, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

8.2CVE-2025-53652jenkins projectjenkins git parameter plugin+2
EPSS score
0.67%
Jenkins Git Parameter Plugin 439.vb_0e46ca_14534 and earlier does not validate that the Git parameter value submitted to the build matches one of the offered choices, allowing attackers with Item/Build permission to inject arbitrary values into Git parameters.5.4CVE-2020-2112jenkins projectjenkins git parameter plugin+2
EPSS score
0.73%
Jenkins Git Parameter Plugin 0.9.11 and earlier does not escape the parameter name shown on the UI, resulting in a stored cross-site scripting vulnerability exploitable by users with Job/Configure permission.5.4CVE-2020-2238jenkins projectjenkins git parameter plugin+2
EPSS score
0.75%
Jenkins Git Parameter Plugin 0.9.12 and earlier does not escape the repository field on the 'Build with Parameters' page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Job/Configure permission.5.4CVE-2020-2113jenkins projectjenkins git parameter plugin+2
EPSS score
0.73%
Jenkins Git Parameter Plugin 0.9.11 and earlier does not escape the default value shown on the UI, resulting in a stored cross-site scripting vulnerability exploitable by users with Job/Configure permission.5.4CVE-2022-29040jenkins projectjenkins git parameter plugin+2
EPSS score
0.83%
Jenkins Git Parameter Plugin 0.9.15 and earlier does not escape the name and description of Git parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.4.3CVE-2026-57286jenkins projectjenkins git parameter plugin+2
EPSS score
0.28%
A missing permission check in Jenkins Git Parameter Plugin 462.vdcf3df2ed2ca_ and earlier allows attackers with Item/Read permission to obtain information about the SCM repository used by a job, such as branch names, tag names, and revision metadata.