CVE-2026-24494: Order Up Online Ordering System · SQL Injection
Affects Order Up Online Ordering SystemSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 30 Oct 2026, 06:59 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% 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 23 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Order UpOnline Ordering System | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-24494, organizations should immediately implement the following specific actions: 1) Apply any available patches or updates from the vendor as soon as they are released. 2) If patches are not yet available, implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts targeting the /api/integrations/getintegrations endpoint, focusing on anomalous store_id parameter values. 3) Conduct thorough input validation and sanitization on all parameters, especially store_id, ensuring only expected data types and formats are accepted. 4) Employ parameterized queries or prepared statements in the backend code to prevent SQL injection. 5) Restrict database permissions for the application user to the minimum necessary, limiting the potential damage from exploitation. 6) Monitor database logs and application logs for unusual queries or errors indicative of injection attempts. 7) Consider temporarily disabling or restricting access to the vulnerable endpoint if feasible until a patch is applied. 8) Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases. These measures collectively reduce the risk of exploitation and limit potential damage.
Description
SQL Injection vulnerability in the /api/integrations/getintegrations endpoint of Order Up Online Ordering System 1.0 allows an unauthenticated attacker to access sensitive backend database data via a crafted store_id parameter in a POST request.