{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:qmetry-test-management. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53659 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53659 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53659 is a medium-severity vulnerability in Jenkins QMetry Test Management 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-53659 and fix it if it is affected.\n\nWhat it is: CVE-2025-53659 is a medium-severity vulnerability in Jenkins QMetry Test Management 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-53659 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:qmetry-test-management (Maven): affected all versions up to 1.13; no fix listed\n- org.jenkins-ci.plugins:qmetry-test-management (Maven): affected all versions up to 1.13; 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-53659/ (Markdown: https://insights.sbomify.com/CVE-2025-53659/index.md)","id":"CVE-2025-53659","markdown":"https://insights.sbomify.com/CVE-2025-53659/index.md","name":"CVE-2025-53659","record":{"aliases":["GHSA-p9gh-rpjw-78qg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins QMetry plugin","requires_auth":"low_privilege","summary":"Attackers with extended read permissions or file system access can view unencrypted QMetry API keys stored in Jenkins job configurations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"qmetry_test_management","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-311","name":"Missing Encryption of Sensitive Data"}],"description":"Jenkins QMetry Test Management Plugin 1.13 and earlier stores Qmetry Automation API Keys 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 QMetry Test Management Plugin stores unencrypted API keys","id":"CVE-2025-53659","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 QMetry Test Management Plugin vulnerability exposes API keys","id":"CVE-2025-53660"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.13"],"package":"org.jenkins-ci.plugins:qmetry-test-management","purl":null,"source":"GHSA-p9gh-rpjw-78qg"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.13"],"package":"org.jenkins-ci.plugins:qmetry-test-management","purl":"pkg:maven/org.jenkins-ci.plugins/qmetry-test-management","source":"GHSA-p9gh-rpjw-78qg"}],"prev":{"headline":"Jenkins Applitools Eyes Plugin vulnerable to XSS through its Build page","id":"CVE-2025-53658"},"products":["Jenkins QMetry Test Management Plugin"],"published":"2025-07-09","related":[{"cvss_score":4.3,"headline":"Jenkins QMetry Test Management Plugin vulnerability exposes API keys","id":"CVE-2025-53660","kev_date_added":null,"published":"2025-07-09"}],"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 extended read permissions or file system access can view unencrypted QMetry API keys stored in Jenkins job configurations.","url":"https://insights.sbomify.com/CVE-2025-53659/"}