{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-60249 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-60249 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-60249 is a medium-severity cross-site scripting vulnerability in CIRCL vulnerability-lookup, published on 25 Sep 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-60249 and fix it if it is affected.\n\nWhat it is: CVE-2025-60249 is a medium-severity cross-site scripting vulnerability in CIRCL vulnerability-lookup, published on 25 Sep 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-60249 in the wild and no public exploit code.\n\nAffected product: CIRCL vulnerability-lookup. 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-60249/ (Markdown: https://insights.sbomify.com/CVE-2025-60249/index.md)","id":"CVE-2025-60249","markdown":"https://insights.sbomify.com/CVE-2025-60249/index.md","name":"CVE-2025-60249","record":{"aliases":["GHSA-9737-qv54-hq49"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Vulnerability lookup tool","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary JavaScript via unsanitized user input in bundles, comments, or sightings, potentially leading to code execution or account takeover.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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":"vulnerability-lookup 2.16.0 allows XSS in bundle.py, comment.py, and user.py, by a user on a vulnerability-lookup instance who can add bundles, comments, or sightings. A cross-site scripting (XSS) vulnerability was discovered in the handling of user-supplied input in the Bundles, Comments, and Sightings components. Untrusted data was not properly sanitized before being rendered in templates and tables, which could allow attackers to inject arbitrary JavaScript into the application. The issue was due to unsafe use of innerHTML and insufficient validation of dynamic URLs and model fields. This vulnerability has been fixed by escaping untrusted data, replacing innerHTML assignments with safer DOM methods, encoding URLs with encodeURIComponent, and improving input validation in the affected models.","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 vulnerability-lookup","id":"CVE-2025-60249","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in B2","id":"CVE-2025-60250"},"packages":[],"prev":{"headline":"WordPress WPC Product Options for WooCommerce plugin \u003c= 3.1.3 - Local File Inclusion vulnerability","id":"CVE-2025-60248"},"products":["vulnerability-lookup"],"published":"2025-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-26","vendors":["CIRCL"]},"summary":"Attackers can inject arbitrary JavaScript via unsanitized user input in bundles, comments, or sightings, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2025-60249/"}