{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45956 exists.","fix":"No fix has been published for CVE-2025-45956 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-45956 is a high-severity SQL injection vulnerability in n/a, published on 29 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-45956 and fix it if it is affected.\n\nWhat it is: CVE-2025-45956 is a high-severity SQL injection vulnerability in n/a, published on 29 Apr 2025. 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-2025-45956 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-2025-45956/ (Markdown: https://insights.sbomify.com/CVE-2025-45956/index.md)","id":"CVE-2025-45956","markdown":"https://insights.sbomify.com/CVE-2025-45956/index.md","name":"CVE-2025-45956","record":{"aliases":["GHSA-3rr5-vgfq-8c8h"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Computer Laboratory Management System","requires_auth":"low_privilege","summary":"An authenticated attacker can execute arbitrary SQL commands via the id parameter in manage_damage.php, 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":"computer_laboratory_management_system","vendor":"oretnom23"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A SQL injection vulnerability in manage_damage.php in Sourcecodester Computer Laboratory Management System v1.0 allows an authenticated attacker to execute arbitrary SQL commands via the \"id\" parameter","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2025-45956","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CVE RECORD.","id":"CVE-2025-45959"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-45953"},"products":["n/a"],"published":"2025-04-29","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-34479","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-34480","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-31546","kev_date_added":null,"published":"2024-04-19"},{"cvss_score":9.4,"headline":"SQL injection in n/a","id":"CVE-2024-31545","kev_date_added":null,"published":"2024-04-22"},{"cvss_score":9.1,"headline":"SQL injection in n/a","id":"CVE-2024-31547","kev_date_added":null,"published":"2024-04-19"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2024-54818","kev_date_added":null,"published":"2025-01-08"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-06","vendors":["n/a"]},"summary":"An authenticated attacker can execute arbitrary SQL commands via the id parameter in manage_damage.php, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2025-45956/"}