{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-4975 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-4975 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4975 is a low-severity cross-site scripting vulnerability in n/a, published on 25 Sep 2006. 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-2006-4975 and fix it if it is affected.\n\nWhat it is: CVE-2006-4975 is a low-severity cross-site scripting vulnerability in n/a, published on 25 Sep 2006. 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-2006-4975 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-2006-4975/ (Markdown: https://insights.sbomify.com/CVE-2006-4975/index.md)","id":"CVE-2006-4975","markdown":"https://insights.sbomify.com/CVE-2006-4975/index.md","name":"CVE-2006-4975","record":{"aliases":["GHSA-6c46-vqrp-wg6q"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Yahoo Messenger WAP","requires_auth":"none","summary":"Attackers can inject arbitrary web script or HTML into Yahoo! Messenger for WAP via URLs, requiring user interaction to execute.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"messenger","vendor":"yahoo"}],"cvss":{"score":2.6,"severity":"low","source":"nvd","vector":"AV:N/AC:H/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"Yahoo! Messenger for WAP permits saving messages that contain JavaScript, which allows user-assisted remote attackers to inject arbitrary web script or HTML via a URL at the online service.","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-2006-4975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2006-4976"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2006-4974"},"products":["n/a"],"published":"2006-09-25","related":[{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2014-7216","kev_date_added":null,"published":"2015-09-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-4515","kev_date_added":null,"published":"2007-08-31"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-4391","kev_date_added":null,"published":"2007-08-17"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-3147","kev_date_added":null,"published":"2007-06-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-3148","kev_date_added":null,"published":"2007-06-11"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-1680","kev_date_added":null,"published":"2007-04-06"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2006-6603","kev_date_added":null,"published":"2006-12-15"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Attackers can inject arbitrary web script or HTML into Yahoo! Messenger for WAP via URLs, requiring user interaction to execute.","url":"https://insights.sbomify.com/CVE-2006-4975/"}