{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4225 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4225 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4225 is a high-severity SQL injection vulnerability in n/a, published on 14 Dec 2005. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-4225 and fix it if it is affected.\n\nWhat it is: CVE-2005-4225 is a high-severity SQL injection vulnerability in n/a, published on 14 Dec 2005. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-4225 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-4225/ (Markdown: https://insights.sbomify.com/CVE-2005-4225/index.md)","id":"CVE-2005-4225","markdown":"https://insights.sbomify.com/CVE-2005-4225/index.md","name":"CVE-2005-4225","record":{"aliases":["GHSA-65vm-wjw5-2x4h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"myBloggie web application","requires_auth":"unknown","summary":"Remote attackers can execute arbitrary SQL commands via multiple parameters in myBloggie, 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":"mybloggie","vendor":"mywebland"}],"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":"Multiple \"potential\" SQL injection vulnerabilities in myBloggie 2.1.3 beta might allow remote attackers to execute arbitrary SQL commands via (1) the category parameter in add.php, (2) the cat_desc parameter in addcat.php, (3) the level and user parameters in adduser.php, (4) the post_id parameter in del.php, (5) the cat_id parameter in delcat.php, (6) the comment_id parameter in delcomment.php, (7) the id parameter in deluser.php, (8) the post_id and category parameter in edit.php, (9) the cat_id and cat_desc parameters in editcat.php, and (10) the id, level, and user parameters in edituser.php.  NOTE: the username/login.php vector is already identified by CVE-2005-2838.","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":"SQL injection in n/a","id":"CVE-2005-4225","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2005"},"n_packages":0,"n_references":17,"next":{"headline":"SQL injection in n/a","id":"CVE-2005-4226"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2005-4224"},"products":["n/a"],"published":"2005-12-14","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2007-3194","kev_date_added":null,"published":"2007-06-12"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-3003","kev_date_added":null,"published":"2007-06-04"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-4042","kev_date_added":null,"published":"2006-08-09"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-3905","kev_date_added":null,"published":"2006-07-27"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2006-2859","kev_date_added":null,"published":"2006-06-06"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-3153","kev_date_added":null,"published":"2005-10-05"}],"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 execute arbitrary SQL commands via multiple parameters in myBloggie, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2005-4225/"}