{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:warrior. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53675 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53675 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53675 is a medium-severity vulnerability in Jenkins Warrior Framework Plugin, published on 9 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53675 and fix it if it is affected.\n\nWhat it is: CVE-2025-53675 is a medium-severity vulnerability in Jenkins Warrior Framework Plugin, published on 9 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-53675 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:warrior (Maven): affected all versions up to 1.2; no fix listed\n- org.jenkins-ci.plugins:warrior (Maven): affected all versions up to 1.2; no fix listed\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-53675/ (Markdown: https://insights.sbomify.com/CVE-2025-53675/index.md)","id":"CVE-2025-53675","markdown":"https://insights.sbomify.com/CVE-2025-53675/index.md","name":"CVE-2025-53675","record":{"aliases":["GHSA-2g8w-9933-36vr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers with specific permissions or file system access can view unencrypted passwords stored in Jenkins job configuration files.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"warrior_framework","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-256","name":"Plaintext Storage of a Password"}],"description":"Jenkins Warrior Framework Plugin 1.2 and earlier stores passwords unencrypted in job config.xml files on the Jenkins controller, where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Jenkins Warrior Framework Plugin vulnerability exposes unencrypted passwords to certain authenticated users","id":"CVE-2025-53675","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins Xooa Plugin vulnerability exposes unencrypted tokens to authenticated users","id":"CVE-2025-53676"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.2"],"package":"org.jenkins-ci.plugins:warrior","purl":null,"source":"GHSA-2g8w-9933-36vr"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.2"],"package":"org.jenkins-ci.plugins:warrior","purl":"pkg:maven/org.jenkins-ci.plugins/warrior","source":"GHSA-2g8w-9933-36vr"}],"prev":{"headline":"Jenkins Sensedia API Platform Plugin vulnerability exposes unencrypted tokens","id":"CVE-2025-53674"},"products":["Jenkins Warrior Framework Plugin"],"published":"2025-07-09","related":[],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["Jenkins Project"]},"summary":"Attackers with specific permissions or file system access can view unencrypted passwords stored in Jenkins job configuration files.","url":"https://insights.sbomify.com/CVE-2025-53675/"}