Git Parameter vulnerabilitiesRanked by how likely they are to be used.
Git Parameter is made by Jenkins. We track 5 published vulnerabilities in it, across 36 versions. None of them is on the list of flaws known to be exploited today. If you run Git Parameter, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Git Parameter vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Git Parameter's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Git Parameter flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.8%CVE-2022-29040Medium
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...
- 0.8%CVE-2020-2238Medium
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...
- 0.7%CVE-2020-2112Medium
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.
- 0.7%CVE-2020-2113Medium
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.
- 0.7%CVE-2025-53652High
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...
Running Git Parameter? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Git Parameter on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 5 published vulnerabilities listed under the name Git Parameter, across 36 versions.
None of Git Parameter's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Git Parameter. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.