{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-56173 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-56173 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-56173 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Dec 2024. 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-2024-56173 and fix it if it is affected.\n\nWhat it is: CVE-2024-56173 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Dec 2024. 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-2024-56173 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-2024-56173/ (Markdown: https://insights.sbomify.com/CVE-2024-56173/index.md)","id":"CVE-2024-56173","markdown":"https://insights.sbomify.com/CVE-2024-56173/index.md","name":"CVE-2024-56173","record":{"aliases":["GHSA-jwm8-5prh-37pj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Optimizely Configured Commerce","requires_auth":"none","summary":"Attackers can execute malicious JavaScript in users' browsers via crafted SVG documents in Optimizely Configured Commerce.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"configured_commerce","vendor":"optimizely"}],"cvss":{"score":4.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed in users' browsers under specific conditions: XSS from JavaScript in an SVG document.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2024-56173","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-56174"},"packages":[],"prev":{"headline":"Use after free in libxml2","id":"CVE-2024-56171"},"products":["n/a"],"published":"2024-12-18","related":[{"cvss_score":8.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-56174","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":7.5,"headline":"Business logic in n/a","id":"CVE-2025-22384","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2025-22387","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":7.3,"headline":"Security feature bypass in n/a","id":"CVE-2025-22386","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-56175","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":5.9,"headline":"Missing authorization in n/a","id":"CVE-2025-22385","kev_date_added":null,"published":"2025-01-04"}],"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":"2024-12-18","vendors":["n/a"]},"summary":"Attackers can execute malicious JavaScript in users' browsers via crafted SVG documents in Optimizely Configured Commerce.","url":"https://insights.sbomify.com/CVE-2024-56173/"}