{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-56154 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-56154 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56154 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-56154 and fix it if it is affected.\n\nWhat it is: CVE-2025-56154 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-56154 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-56154/ (Markdown: https://insights.sbomify.com/CVE-2025-56154/index.md)","id":"CVE-2025-56154","markdown":"https://insights.sbomify.com/CVE-2025-56154/index.md","name":"CVE-2025-56154","record":{"aliases":["GHSA-4xvq-93jj-7c4r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"htmly web application","requires_auth":"none","summary":"Attackers can inject arbitrary JavaScript via the name parameter in the author endpoint, potentially executing code in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"htmly","vendor":"htmly"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"htmly v3.0.8 is vulnerable to Cross Site Scripting (XSS) in the /author/:name endpoint of the affected application. The name parameter is not properly sanitized before being reflected in the HTML response, allowing attackers to inject arbitrary JavaScript payloads.","ecosystems":[],"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":"Cross-site scripting in n/a","id":"CVE-2025-56154","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-56157"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2025-56146"},"products":["n/a"],"published":"2025-10-02","related":[{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2021-36701","kev_date_added":null,"published":"2021-08-03"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2021-33354","kev_date_added":null,"published":"2022-09-30"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2021-40285","kev_date_added":null,"published":"2022-08-26"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2024-34191","kev_date_added":null,"published":"2024-05-14"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2020-23766","kev_date_added":null,"published":"2021-05-21"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-30953","kev_date_added":null,"published":"2024-04-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-01-20","vendors":["n/a"]},"summary":"Attackers can inject arbitrary JavaScript via the name parameter in the author endpoint, potentially executing code in victim browsers.","url":"https://insights.sbomify.com/CVE-2025-56154/"}