{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30530 exists.","fix":"No fix has been published for CVE-2026-30530 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-30530 is a critical SQL injection vulnerability in n/a, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-30530 and fix it if it is affected.\n\nWhat it is: CVE-2026-30530 is a critical SQL injection vulnerability in n/a, published on 27 Mar 2026. 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-2026-30530 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-2026-30530/ (Markdown: https://insights.sbomify.com/CVE-2026-30530/index.md)","id":"CVE-2026-30530","markdown":"https://insights.sbomify.com/CVE-2026-30530/index.md","name":"CVE-2026-30530","record":{"aliases":["GHSA-wvwf-q453-j6fr"],"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 Food Ordering System","requires_auth":"none","summary":"Attackers can inject malicious SQL commands via the username parameter in the save_customer action, 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":"online_food_ordering_system","vendor":"oretnom23"}],"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":"A SQL Injection vulnerability exists in SourceCodester Online Food Ordering System v1.0 in the Actions.php file (specifically the save_customer action). The application fails to properly sanitize user input supplied to the \"username\" parameter. This allows an attacker to inject malicious SQL commands.","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-2026-30530","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2026-30531"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2026-30529"},"products":["n/a"],"published":"2026-03-27","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2026-30532","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2026-30533","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-30122","kev_date_added":null,"published":"2023-05-05"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-24646","kev_date_added":null,"published":"2023-02-13"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-29297","kev_date_added":null,"published":"2023-01-20"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-36759","kev_date_added":null,"published":"2022-09-02"}],"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":"2026-03-27","vendors":["n/a"]},"summary":"Attackers can inject malicious SQL commands via the username parameter in the save_customer action, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2026-30530/"}