{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0955 exists.","fix":"No fix has been published for CVE-2002-0955 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-0955 is a high-severity cross-site scripting vulnerability in n/a, published on 31 Aug 2002. 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-2002-0955 and fix it if it is affected.\n\nWhat it is: CVE-2002-0955 is a high-severity cross-site scripting vulnerability in n/a, published on 31 Aug 2002. 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-2002-0955 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-2002-0955/ (Markdown: https://insights.sbomify.com/CVE-2002-0955/index.md)","id":"CVE-2002-0955","markdown":"https://insights.sbomify.com/CVE-2002-0955/index.md","name":"CVE-2002-0955","record":{"aliases":["GHSA-rxvx-4qf3-f363"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"YaBB bulletin board","requires_auth":"none","summary":"Remote attackers can execute arbitrary scripts in other users' browsers via the num parameter in YaBB.cgi, potentially leading to session hijacking.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yabb","vendor":"yabb"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Cross-site scripting vulnerability in YaBB.cgi for Yet Another Bulletin Board (YaBB) 1 Gold SP1 and earlier allows remote attackers to execute arbitrary script as other web site visitors via script in the num parameter, which is not filtered in the resulting error message.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2002-06-21","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2002-06-21","kind":"exploitdb","ref":"21573","stars":null,"title":"YaBB 1 - Invalid Topic Error Page Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2002-0955","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2002"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2002-0956"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2002-0954"},"products":["n/a"],"published":"2002-08-31","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2007-3208","kev_date_added":null,"published":"2007-06-14"},{"cvss_score":10,"headline":"Cross-site request forgery in n/a","id":"CVE-2004-2403","kev_date_added":null,"published":"2005-08-17"},{"cvss_score":10,"headline":"SQL injection in n/a","id":"CVE-2004-0343","kev_date_added":null,"published":"2004-03-18"},{"cvss_score":9.8,"headline":"Path traversal in YaBB","id":"CVE-2013-2057","kev_date_added":null,"published":"2020-02-11"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-3275","kev_date_added":null,"published":"2006-06-28"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2004-2139","kev_date_added":null,"published":"2005-06-30"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary scripts in other users' browsers via the num parameter in YaBB.cgi, potentially leading to session hijacking.","url":"https://insights.sbomify.com/CVE-2002-0955/"}