{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51968 exists.","fix":"No fix has been published for CVE-2025-51968 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-51968 is a medium-severity SQL injection vulnerability in n/a, published on 28 Aug 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-51968 and fix it if it is affected.\n\nWhat it is: CVE-2025-51968 is a medium-severity SQL injection vulnerability in n/a, published on 28 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51968 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-51968/ (Markdown: https://insights.sbomify.com/CVE-2025-51968/index.md)","id":"CVE-2025-51968","markdown":"https://insights.sbomify.com/CVE-2025-51968/index.md","name":"CVE-2025-51968","record":{"aliases":["GHSA-xqj4-vchj-vm63"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Online Shopping System","requires_auth":"none","summary":"Attackers can inject arbitrary SQL via the proId parameter in action.php, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"online_shopping_system_advanced","vendor":"puneethreddyhc"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A SQL Injection vulnerability exists in the action.php file of PuneethReddyHC Online Shopping System Advanced 1.0. The application fails to properly sanitize user-supplied input in the proId POST parameter, allowing attackers to inject arbitrary SQL expressions.","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-51968","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":"SQL injection in n/a","id":"CVE-2025-51969"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-51967"},"products":["n/a"],"published":"2025-08-28","related":[{"cvss_score":8.7,"headline":"Online Shopping System Advanced 1.0 SQL Injection via Payment Success Parameter","id":"CVE-2024-58316","kev_date_added":null,"published":"2025-12-12"},{"cvss_score":7.7,"headline":"SQL injection in n/a","id":"CVE-2025-51970","kev_date_added":null,"published":"2025-07-29"},{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2025-51969","kev_date_added":null,"published":"2025-08-28"},{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2025-51972","kev_date_added":null,"published":"2025-08-28"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2025-51971","kev_date_added":null,"published":"2025-08-28"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-08-28","vendors":["n/a"]},"summary":"Attackers can inject arbitrary SQL via the proId parameter in action.php, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2025-51968/"}