{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:curseforge-publisher. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64147 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-64147 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64147 is a medium-severity vulnerability in Jenkins Curseforge Publisher Plugin, published on 29 Oct 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-64147 and fix it if it is affected.\n\nWhat it is: CVE-2025-64147 is a medium-severity vulnerability in Jenkins Curseforge Publisher Plugin, published on 29 Oct 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-64147 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:curseforge-publisher (Maven): affected all versions up to 1.0; no fix listed\n- org.jenkins-ci.plugins:curseforge-publisher (Maven): affected all versions up to 1.0; 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-64147/ (Markdown: https://insights.sbomify.com/CVE-2025-64147/index.md)","id":"CVE-2025-64147","markdown":"https://insights.sbomify.com/CVE-2025-64147/index.md","name":"CVE-2025-64147","record":{"aliases":["GHSA-hv42-crpx-q355"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers can view exposed API keys in the Jenkins Curseforge Publisher Plugin configuration form, potentially leading to credential theft.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"curseforge_publisher","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-311","name":"Missing Encryption of Sensitive Data"}],"description":"Jenkins Curseforge Publisher Plugin 1.0 does not mask 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 Curseforge Publisher Plugin does not mask API Keys displayed on the job configuration form","id":"CVE-2025-64147","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 Publish to Bitbucket Plugin is missing a permissions check","id":"CVE-2025-64148"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.0"],"package":"org.jenkins-ci.plugins:curseforge-publisher","purl":null,"source":"GHSA-hv42-crpx-q355"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.0"],"package":"org.jenkins-ci.plugins:curseforge-publisher","purl":"pkg:maven/org.jenkins-ci.plugins/curseforge-publisher","source":"GHSA-hv42-crpx-q355"}],"prev":{"headline":"Jenkins Curseforge Publisher Plugin stores API Keys unencrypted in job config.xml files","id":"CVE-2025-64146"},"products":["Jenkins Curseforge Publisher Plugin"],"published":"2025-10-29","related":[{"cvss_score":4.3,"headline":"Jenkins Curseforge Publisher Plugin stores API Keys unencrypted in job config.xml files","id":"CVE-2025-64146","kev_date_added":null,"published":"2025-10-29"}],"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 exposed API keys in the Jenkins Curseforge Publisher Plugin configuration form, potentially leading to credential theft.","url":"https://insights.sbomify.com/CVE-2025-64147/"}