{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63607 exists.","fix":"No fix has been published for CVE-2025-63607 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63607 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Aug 2026. 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-63607 and fix it if it is affected.\n\nWhat it is: CVE-2025-63607 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63607 exists.\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-63607/ (Markdown: https://insights.sbomify.com/CVE-2025-63607/index.md)","id":"CVE-2025-63607","markdown":"https://insights.sbomify.com/CVE-2025-63607/index.md","name":"CVE-2025-63607","record":{"aliases":["GHSA-j8wf-qxgq-3c7m"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"TechStore web application","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript in users' browsers via the id parameter in contact_display, potentially leading to session hijacking or data theft.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"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":"TechStore 1.0 is vulnerable to Cross Site Scripting (XSS). In contact_display, the application echoes the id parameter verbatim into the rendered page, permitting execution of attacker-supplied JavaScript in users browser.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2025-63607","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-63608"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2025-63604"},"products":["n/a"],"published":"2026-08-31","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["n/a"]},"summary":"Attackers can execute arbitrary JavaScript in users' browsers via the id parameter in contact_display, potentially leading to session hijacking or data theft.","url":"https://insights.sbomify.com/CVE-2025-63607/"}