CVE-2026-30530: Online-Food-Ordering-System · SQL Injection
Affects Online-Food-Ordering-SystemSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmeifukun/Online-Food-Ordering-Systempkg:github/meifukun/Online-Food-Ordering-SystemOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, organizations should immediately implement strict input validation and sanitization for all user-supplied data, especially the 'username' parameter in the save_customer action. Employing parameterized queries or prepared statements is critical to prevent SQL Injection attacks. Code review and security testing should be conducted to identify and remediate similar vulnerabilities throughout the application. If possible, isolate the database with least privilege access controls to limit the impact of any successful injection. Monitoring database logs for suspicious queries can help detect exploitation attempts. Organizations should also stay alert for official patches or updates from the vendor and apply them promptly once available. As a longer-term measure, adopting secure coding standards and conducting regular security assessments will reduce the risk of injection vulnerabilities.
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.