{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:htmlpublisher. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53651 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:htmlpublisher to 427 or later.","what":"CVE-2025-53651 is a medium-severity vulnerability in Jenkins HTML Publisher 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-53651 and fix it if it is affected.\n\nWhat it is: CVE-2025-53651 is a medium-severity vulnerability in Jenkins HTML Publisher 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-53651 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:htmlpublisher (Maven): affected all versions; fixed in 427\n- org.jenkins-ci.plugins:htmlpublisher (Maven): affected all versions; fixed in 427\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-53651/ (Markdown: https://insights.sbomify.com/CVE-2025-53651/index.md)","id":"CVE-2025-53651","markdown":"https://insights.sbomify.com/CVE-2025-53651/index.md","name":"CVE-2025-53651","record":{"aliases":["GHSA-367v-5ppj-2hrx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins HTML Publisher Plugin","requires_auth":"low_privilege","summary":"Attackers can view absolute file system paths in build logs, exposing internal Jenkins controller structure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"html_publisher","vendor":"jenkins"}],"cvss":{"score":6.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-36","name":"Absolute Path Traversal"}],"description":"Jenkins HTML Publisher Plugin 425 and earlier displays log messages that include the absolute paths of files archived during the Publish HTML reports post-build step, exposing information about the Jenkins controller file system in the build log.","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":true,"headline":"Jenkins HTML Publisher Plugin vulnerability displays controller file system information in its logs","id":"CVE-2025-53651","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 Git Parameter Plugin vulnerable to code injection due to inexhaustive parameter check","id":"CVE-2025-53652"},"packages":[{"ecosystem":"Maven","fixed":["427"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:htmlpublisher","purl":null,"source":"GHSA-367v-5ppj-2hrx"},{"ecosystem":"Maven","fixed":["427"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:htmlpublisher","purl":"pkg:maven/org.jenkins-ci.plugins/htmlpublisher","source":"GHSA-367v-5ppj-2hrx"}],"prev":{"headline":"Jenkins Credentials Binding Plugin vulnerability can expose sensitive information in logger messages","id":"CVE-2025-53650"},"products":["Jenkins HTML Publisher Plugin"],"published":"2025-07-09","related":[{"cvss_score":8,"headline":"Jenkins HTML Publisher Plugin has a XSS vulnerability in the legacy wrapper file","id":"CVE-2026-42524","kev_date_added":null,"published":"2026-04-29"},{"cvss_score":6.5,"headline":"Jenkins HTML Publisher Plugin does not properly sanitize input","id":"CVE-2024-28149","kev_date_added":null,"published":"2024-03-06"},{"cvss_score":6.5,"headline":"Jenkins HTML Publisher Plugin path traversal vulnerability","id":"CVE-2018-1000175","kev_date_added":null,"published":"2018-05-08"},{"cvss_score":5.4,"headline":"Jenkins HTML Publisher Plugin vulnerable to Cross-site Scripting","id":"CVE-2019-10432","kev_date_added":null,"published":"2019-10-01"},{"cvss_score":4.7,"headline":"Jenkins HTML Publisher Plugin Stored XSS vulnerability","id":"CVE-2024-28150","kev_date_added":null,"published":"2024-03-06"},{"cvss_score":4.3,"headline":"Jenkins HTML Publisher Plugin Path traversal vulnerability","id":"CVE-2024-28151","kev_date_added":null,"published":"2024-03-06"}],"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 absolute file system paths in build logs, exposing internal Jenkins controller structure.","url":"https://insights.sbomify.com/CVE-2025-53651/"}