{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1708 exists.","fix":"No fix has been published for CVE-2002-1708 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1708 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jun 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2002-1708 and fix it if it is affected.\n\nWhat it is: CVE-2002-1708 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jun 2005. Any signed-in user can exploit it over the network, 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-1708 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-1708/ (Markdown: https://insights.sbomify.com/CVE-2002-1708/index.md)","id":"CVE-2002-1708","markdown":"https://insights.sbomify.com/CVE-2002-1708/index.md","name":"CVE-2002-1708","record":{"aliases":["GHSA-cqxq-6p9g-3g96"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Webmail application","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary scripts in other users' browsers via XSS in BasiliX Webmail subject or message fields.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"basilix_webmail","vendor":"basilix"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Cross-site scripting vulnerability (XSS) in BasiliX Webmail 1.10 allows remote attackers to execute arbitrary script as other users by injecting script into the (1) subject or (2) message fields.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2002-06-19","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2002-06-19","kind":"exploitdb","ref":"21570","stars":null,"title":"BasiliX Webmail 1.1 - Message Content Script Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2002-1708","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2002"},"n_packages":0,"n_references":4,"next":{"headline":"SQL injection in n/a","id":"CVE-2002-1709"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2002-1707"},"products":["n/a"],"published":"2005-06-21","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2001-1044","kev_date_added":null,"published":"2002-02-02"},{"cvss_score":6.4,"headline":"SQL injection in n/a","id":"CVE-2002-1709","kev_date_added":null,"published":"2005-06-21"},{"cvss_score":5.1,"headline":"File upload in n/a","id":"CVE-2006-5167","kev_date_added":null,"published":"2006-10-04"},{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2001-1045","kev_date_added":null,"published":"2002-02-02"},{"cvss_score":3.6,"headline":"Information disclosure in n/a","id":"CVE-2002-1710","kev_date_added":null,"published":"2005-06-21"},{"cvss_score":2.1,"headline":"Information disclosure in n/a","id":"CVE-2002-1711","kev_date_added":null,"published":"2005-06-21"}],"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 XSS in BasiliX Webmail subject or message fields.","url":"https://insights.sbomify.com/CVE-2002-1708/"}