{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.tools:git-parameter. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53652 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.tools:git-parameter to 444.vca or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-53652 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-53652 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.tools:git-parameter (Maven): affected all versions; fixed in 444.vca\n- org.jenkins-ci.tools:git-parameter (Maven): affected all versions; fixed in 444.vca\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-53652/ (Markdown: https://insights.sbomify.com/CVE-2025-53652/index.md)","id":"CVE-2025-53652","markdown":"https://insights.sbomify.com/CVE-2025-53652/index.md","name":"CVE-2025-53652","record":{"aliases":["GHSA-qcj2-99cg-mppf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Git Parameter Plugin","requires_auth":"none","summary":"Attackers with build permissions can inject arbitrary values into Git parameters due to missing validation of submitted choices.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"git_parameter","vendor":"jenkins"}],"cvss":{"score":8.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2025-07-25","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-07-25T13:10:17Z","kind":"github_poc","ref":"https://github.com/pl4tyz/CVE-2025-53652-Jenkins-Git-Parameter-Analysis","stars":2,"title":"CVE-2025-53652: Jenkins Git Parameter Analysis"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Jenkins Git Parameter Plugin vulnerable to code injection due to inexhaustive parameter check","id":"CVE-2025-53652","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"other","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins Aqua Security Scanner Plugin vulnerability exposes scanner tokens","id":"CVE-2025-53653"},"packages":[{"ecosystem":"Maven","fixed":["444.vca"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.tools:git-parameter","purl":null,"source":"GHSA-qcj2-99cg-mppf"},{"ecosystem":"Maven","fixed":["444.vca"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.tools:git-parameter","purl":"pkg:maven/org.jenkins-ci.tools/git-parameter","source":"GHSA-qcj2-99cg-mppf"}],"prev":{"headline":"Jenkins HTML Publisher Plugin vulnerability displays controller file system information in its logs","id":"CVE-2025-53651"},"products":["Jenkins Git Parameter Plugin"],"published":"2025-07-09","related":[{"cvss_score":5.4,"headline":"Stored XSS vulnerability in Jenkins Git Parameter Plugin","id":"CVE-2022-29040","kev_date_added":null,"published":"2022-04-12"},{"cvss_score":5.4,"headline":"Stored XSS vulnerability in Jenkins Git Parameter Plugin","id":"CVE-2020-2238","kev_date_added":null,"published":"2020-09-01"},{"cvss_score":5.4,"headline":"Jenkins Git Parameter Plugin vulnerable to Stored cross-site scripting (XSS)","id":"CVE-2020-2112","kev_date_added":null,"published":"2020-02-12"},{"cvss_score":5.4,"headline":"Jenkins Git Parameter Plugin vulnerable to stored cross-site scripting (XSS)","id":"CVE-2020-2113","kev_date_added":null,"published":"2020-02-12"},{"cvss_score":4.3,"headline":"Jenkins Git Parameter Plugin has a missing permission check that allows listing SCM branch and tag names","id":"CVE-2026-57286","kev_date_added":null,"published":"2026-06-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["Jenkins Project"]},"summary":"Attackers with build permissions can inject arbitrary values into Git parameters due to missing validation of submitted choices.","url":"https://insights.sbomify.com/CVE-2025-53652/"}