{"answers":{"affected":"2 open source packages ship an affected version, including io.jenkins.plugins:testsigma. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53661 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53661 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53661 is a medium-severity vulnerability in Jenkins Testsigma Test Plan run 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-53661 and fix it if it is affected.\n\nWhat it is: CVE-2025-53661 is a medium-severity vulnerability in Jenkins Testsigma Test Plan run 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-53661 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.jenkins.plugins:testsigma (Maven): affected all versions up to 1.6; no fix listed\n- io.jenkins.plugins:testsigma (Maven): affected all versions up to 1.6; 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-53661/ (Markdown: https://insights.sbomify.com/CVE-2025-53661/index.md)","id":"CVE-2025-53661","markdown":"https://insights.sbomify.com/CVE-2025-53661/index.md","name":"CVE-2025-53661","record":{"aliases":["GHSA-8wp4-r84g-gcmw"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers can view unmasked Testsigma API keys in the Jenkins job configuration form, potentially leading to unauthorized access to Testsigma services.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"testsigma_test_plan_run","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Jenkins Testsigma Test Plan run Plugin 1.6 and earlier does not mask Testsigma API keys displayed on the job configuration form, increasing the potential for attackers to observe and capture them.","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 Testsigma Test Plan vulnerability exposes API keys via job configuration form","id":"CVE-2025-53661","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 IFTTT Build Notifier Plugin vulnerability exposes IFTTT Maker Channel Keys","id":"CVE-2025-53662"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.6"],"package":"io.jenkins.plugins:testsigma","purl":null,"source":"GHSA-8wp4-r84g-gcmw"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.6"],"package":"io.jenkins.plugins:testsigma","purl":"pkg:maven/io.jenkins.plugins/testsigma","source":"GHSA-8wp4-r84g-gcmw"}],"prev":{"headline":"Jenkins QMetry Test Management Plugin vulnerability exposes API keys","id":"CVE-2025-53660"},"products":["Jenkins Testsigma Test Plan run 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 can view unmasked Testsigma API keys in the Jenkins job configuration form, potentially leading to unauthorized access to Testsigma services.","url":"https://insights.sbomify.com/CVE-2025-53661/"}