{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-46192 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-46192 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46192 is a critical SQL injection vulnerability in n/a, published on 9 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46192 and fix it if it is affected.\n\nWhat it is: CVE-2025-46192 is a critical SQL injection vulnerability in n/a, published on 9 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-46192 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-2025-46192/ (Markdown: https://insights.sbomify.com/CVE-2025-46192/index.md)","id":"CVE-2025-46192","markdown":"https://insights.sbomify.com/CVE-2025-46192/index.md","name":"CVE-2025-46192","record":{"aliases":["GHSA-rvhv-2qpm-56c6"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Client Database Management System","requires_auth":"none","summary":"Attackers can inject SQL commands via the order_id parameter in user_payment_update.php to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"client_database_management_system","vendor":"lerouxyxchire"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"SourceCodester Client Database Management System 1.0 is vulnerable to SQL Injection in user_payment_update.php via the order_id POST 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":"SQL injection in n/a","id":"CVE-2025-46192","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2025-46193"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2025-46191"},"products":["n/a"],"published":"2025-05-09","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-46188","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-46189","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-46190","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-46191","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-46193","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":7.1,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-63711","kev_date_added":null,"published":"2025-11-10"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-10","vendors":["n/a"]},"summary":"Attackers can inject SQL commands via the order_id parameter in user_payment_update.php to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2025-46192/"}