{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-0412 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-0412 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-0412 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Feb 2005. 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-2005-0412 and fix it if it is affected.\n\nWhat it is: CVE-2005-0412 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Feb 2005. 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-2005-0412 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-2005-0412/ (Markdown: https://insights.sbomify.com/CVE-2005-0412/index.md)","id":"CVE-2005-0412","markdown":"https://insights.sbomify.com/CVE-2005-0412/index.md","name":"CVE-2005-0412","record":{"aliases":["GHSA-pc83-5vfx-xhg2"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Spidean PostWrap","requires_auth":"none","summary":"Remote attackers can inject arbitrary HTML and scripts via the page parameter in Spidean PostWrap, requiring user interaction to execute.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"postwrap","vendor":"spidean"}],"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 (XSS) vulnerability in Spidean PostWrap allows remote attackers to inject arbitrary HTML and web script via the page parameter.","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-2005-0412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2005"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2005-0413"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2005-0411"},"products":["n/a"],"published":"2005-02-14","related":[],"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":"Remote attackers can inject arbitrary HTML and scripts via the page parameter in Spidean PostWrap, requiring user interaction to execute.","url":"https://insights.sbomify.com/CVE-2005-0412/"}