# CVE-2025-53652: Jenkins Git Parameter Plugin vulnerable to code injection due to inexhaustive parameter check

> Attackers with build permissions can inject arbitrary values into Git parameters due to missing validation of submitted choices.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-qcj2-99cg-mppf

## What is CVE-2025-53652?

CVE-2025-53652 is a high-severity vulnerability in Jenkins Git Parameter Plugin, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-53652?

2 open source packages ship an affected version, including org.jenkins-ci.tools:git-parameter. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.tools:git-parameter` | Maven | All versions | 444.vca |
| `org.jenkins-ci.tools:git-parameter` | Maven | All versions | 444.vca |

Products: Jenkins Git Parameter.

## How do I fix CVE-2025-53652?

Upgrade org.jenkins-ci.tools:git-parameter to 444.vca or later.

## Is CVE-2025-53652 being exploited?

There is no known exploitation of CVE-2025-53652 in the wild and no public exploit code.

Public exploit code:

- CVE-2025-53652: Jenkins Git Parameter Analysis (github_poc): https://github.com/pl4tyz/CVE-2025-53652-Jenkins-Git-Parameter-Analysis

## Other vulnerabilities in Jenkins Git Parameter Plugin

- [CVE-2022-29040](https://insights.sbomify.com/CVE-2022-29040/): Stored XSS vulnerability in Jenkins Git Parameter Plugin (medium 5.4)
- [CVE-2020-2238](https://insights.sbomify.com/CVE-2020-2238/): Stored XSS vulnerability in Jenkins Git Parameter Plugin (medium 5.4)
- [CVE-2020-2112](https://insights.sbomify.com/CVE-2020-2112/): Jenkins Git Parameter Plugin vulnerable to Stored cross-site scripting (XSS) (medium 5.4)
- [CVE-2020-2113](https://insights.sbomify.com/CVE-2020-2113/): Jenkins Git Parameter Plugin vulnerable to stored cross-site scripting (XSS) (medium 5.4)
- [CVE-2026-57286](https://insights.sbomify.com/CVE-2026-57286/): Jenkins Git Parameter Plugin has a missing permission check that allows listing SCM branch and tag names (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53652 and fix it if it is affected.

What it is: CVE-2025-53652 is a high-severity vulnerability in Jenkins Git Parameter Plugin, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53652 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.tools:git-parameter (Maven): affected all versions; fixed in 444.vca
- org.jenkins-ci.tools:git-parameter (Maven): affected all versions; fixed in 444.vca

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53652/ (Markdown: https://insights.sbomify.com/CVE-2025-53652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53652
- OSV: https://osv.dev/vulnerability/CVE-2025-53652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53652/
Summaries are generated and may contain mistakes; the official description above is the record.