{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-26959 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-26959 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-26959 is a critical SQL injection vulnerability in n/a, published on 27 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26959 and fix it if it is affected.\n\nWhat it is: CVE-2023-26959 is a critical SQL injection vulnerability in n/a, published on 27 Mar 2023. 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-2023-26959 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-2023-26959/ (Markdown: https://insights.sbomify.com/CVE-2023-26959/index.md)","id":"CVE-2023-26959","markdown":"https://insights.sbomify.com/CVE-2023-26959/index.md","name":"CVE-2023-26959","record":{"aliases":["GHSA-cq9w-5wrx-333q"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Park Ticketing System","requires_auth":"none","summary":"Attackers can inject SQL commands via the username parameter to read or modify database contents in the Park Ticketing Management System.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"park_ticketing_management_system","vendor":"phpgurukul"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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":"Phpgurukul Park Ticketing Management System 1.0 is vulnerable to SQL Injection via the User Name 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-2023-26959","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2023-26961"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-26958"},"products":["n/a"],"published":"2023-03-27","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-56074","kev_date_added":null,"published":"2025-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-45017","kev_date_added":null,"published":"2025-04-30"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-45018","kev_date_added":null,"published":"2025-04-30"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-45019","kev_date_added":null,"published":"2025-04-30"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-54811","kev_date_added":null,"published":"2024-12-12"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2025-45020","kev_date_added":null,"published":"2025-04-30"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can inject SQL commands via the username parameter to read or modify database contents in the Park Ticketing Management System.","url":"https://insights.sbomify.com/CVE-2023-26959/"}