{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3963 exists.","fix":"No fix has been published for CVE-2005-3963 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-3963 is a high-severity SQL injection vulnerability in n/a, published on 2 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-3963 and fix it if it is affected.\n\nWhat it is: CVE-2005-3963 is a high-severity SQL injection vulnerability in n/a, published on 2 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3963 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-3963/ (Markdown: https://insights.sbomify.com/CVE-2005-3963/index.md)","id":"CVE-2005-3963","markdown":"https://insights.sbomify.com/CVE-2005-3963/index.md","name":"CVE-2005-3963","record":{"aliases":["GHSA-576v-g6fq-v77x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"DotClear blog software","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary SQL commands via a cookie parameter in DotClear, potentially compromising database integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dotclear","vendor":"dotclear"}],"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":"SQL injection vulnerability in session.php in DotClear before 1.2.3 allows remote attackers to execute arbitrary SQL commands via the dc_xd parameter in a cookie.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2005-12-01","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2005-12-01","kind":"exploitdb","ref":"26689","stars":null,"title":"DotClear 1.2.1/1.2.2 - 'Session.php' SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2005-3963","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2005"},"n_packages":0,"n_references":7,"next":{"headline":"Memory corruption in n/a","id":"CVE-2005-3964"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2005-3962"},"products":["n/a"],"published":"2005-12-02","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2005-3957","kev_date_added":null,"published":"2005-12-01"},{"cvss_score":9.3,"headline":"File upload in n/a","id":"CVE-2008-3232","kev_date_added":null,"published":"2008-07-18"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2015-8832","kev_date_added":null,"published":"2017-02-09"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2016-7902","kev_date_added":null,"published":"2017-01-04"},{"cvss_score":8.7,"headline":"Dotclear 2.25.3 Authenticated Remote Code Execution via File Upload","id":"CVE-2023-53952","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":8.7,"headline":"Dotclear 2.29 Remote Code Execution via Authenticated File Upload","id":"CVE-2024-58281","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":7.5,"headline":"Deserialization in n/a","id":"CVE-2014-1613","kev_date_added":null,"published":"2014-05-16"}],"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 execute arbitrary SQL commands via a cookie parameter in DotClear, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2005-3963/"}