{"answers":{"affected":"2 open source packages ship an affected version, including io.jenkins.plugins:xooa. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53676 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53676 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53676 is a medium-severity vulnerability in Jenkins Xooa 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-53676 and fix it if it is affected.\n\nWhat it is: CVE-2025-53676 is a medium-severity vulnerability in Jenkins Xooa 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-53676 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.jenkins.plugins:xooa (Maven): affected all versions up to 0.0.7; no fix listed\n- io.jenkins.plugins:xooa (Maven): affected all versions up to 0.0.7; 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-53676/ (Markdown: https://insights.sbomify.com/CVE-2025-53676/index.md)","id":"CVE-2025-53676","markdown":"https://insights.sbomify.com/CVE-2025-53676/index.md","name":"CVE-2025-53676","record":{"aliases":["GHSA-56h7-r62c-83qp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Xooa Plugin","requires_auth":"low_privilege","summary":"Attackers with file system access can read unencrypted deployment tokens from the Jenkins controller configuration file.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"xooa","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 Xooa Plugin 0.0.7 and earlier stores the Xooa Deployment Token unencrypted in its global configuration file on the Jenkins controller, where it can be viewed by users with 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 Xooa Plugin vulnerability exposes unencrypted tokens to authenticated users","id":"CVE-2025-53676","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 does not mask its Xooa Deployment Token","id":"CVE-2025-53677"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["0.0.7"],"package":"io.jenkins.plugins:xooa","purl":null,"source":"GHSA-56h7-r62c-83qp"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["0.0.7"],"package":"io.jenkins.plugins:xooa","purl":"pkg:maven/io.jenkins.plugins/xooa","source":"GHSA-56h7-r62c-83qp"}],"prev":{"headline":"Jenkins Warrior Framework Plugin vulnerability exposes unencrypted passwords to certain authenticated users","id":"CVE-2025-53675"},"products":["Jenkins Xooa Plugin"],"published":"2025-07-09","related":[{"cvss_score":5.3,"headline":"Jenkins Xooa Plugin vulnerability does not mask its Xooa Deployment Token","id":"CVE-2025-53677","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 file system access can read unencrypted deployment tokens from the Jenkins controller configuration file.","url":"https://insights.sbomify.com/CVE-2025-53676/"}