{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1049 exists.","fix":"No fix has been published for CVE-2005-1049 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-1049 is a low-severity cross-site scripting vulnerability in n/a, published on 12 Apr 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-1049 and fix it if it is affected.\n\nWhat it is: CVE-2005-1049 is a low-severity cross-site scripting vulnerability in n/a, published on 12 Apr 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1049 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-2005-1049/ (Markdown: https://insights.sbomify.com/CVE-2005-1049/index.md)","id":"CVE-2005-1049","markdown":"https://insights.sbomify.com/CVE-2005-1049/index.md","name":"CVE-2005-1049","record":{"aliases":["GHSA-w42j-5h38-gj7v"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"PostNuke CMS","requires_auth":"none","summary":"Remote attackers can inject arbitrary web script or HTML via specific parameters in PostNuke, particularly when anti-cracker settings are disabled.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"postnuke","vendor":"postnuke_software_foundation"}],"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":"Multiple cross-site scripting vulnerabilities in PostNuke 0.760-RC3 allow remote attackers to inject arbitrary web script or HTML via the (1) module parameter to admin.php or (2) op parameter to user.php. NOTE: the vendor reports that certain issues could not be reproduced for 760 RC3, or for .750.  However, the op/user.php issue exists when the pnAntiCracker setting is disabled.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2005-04-08","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2005-04-08","kind":"exploitdb","ref":"25366","stars":null,"title":"PostNuke Phoenix 0.760 RC3 - 'OP' Cross-Site Scripting"},{"date":"2005-04-08","kind":"exploitdb","ref":"25367","stars":null,"title":"PostNuke Phoenix 0.760 RC3 - 'Module' Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2005-1049","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2005"},"n_packages":0,"n_references":10,"next":{"headline":"Information disclosure in n/a","id":"CVE-2005-1050"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2005-1048"},"products":["n/a"],"published":"2005-04-12","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2007-0386","kev_date_added":null,"published":"2007-01-19"},{"cvss_score":7.8,"headline":"Information disclosure in n/a","id":"CVE-2007-0385","kev_date_added":null,"published":"2007-01-19"},{"cvss_score":7.8,"headline":"Information disclosure in n/a","id":"CVE-2006-6267","kev_date_added":null,"published":"2006-12-04"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-6233","kev_date_added":null,"published":"2006-12-02"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2006-5733","kev_date_added":null,"published":"2006-11-06"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-5121","kev_date_added":null,"published":"2006-10-02"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-2690","kev_date_added":null,"published":"2005-08-24"}],"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-07","vendors":["n/a"]},"summary":"Remote attackers can inject arbitrary web script or HTML via specific parameters in PostNuke, particularly when anti-cracker settings are disabled.","url":"https://insights.sbomify.com/CVE-2005-1049/"}