/

CVE-2026-76050

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Simple Online Food Ordering

CVE-2026-76050

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise and unauthorized data manipulation

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A SQL injection vulnerability in the Simple Online Food Ordering System 1.0 administrative deletion endpoint allows attacker-controlled ID input to influence database queries. If the endpoint is remotely reachable and input is not safely parameterized, an attacker may read, modify, or delete database records.

Affected context

The vulnerability occurs in the administrative AJAX handler at /admin/ajax.php?action=delete_menu when it processes the ID argument. Risk depends on the endpoint being exposed to an attacker and on the application constructing database queries from that value without adequate parameterization or validation.

Exploit preconditions

  • Attack surface: Remotely accessible administrative AJAX endpoint
  • Required access: The ability to submit requests containing a controlled ID value; authentication requirements depend on the deployment's access controls
  • Trigger point: Processing the ID argument in the menu-deletion action
  • Why exploitation is possible: Attacker-controlled input may be incorporated into a database query without being treated strictly as data

Why this happens

The underlying bug is an injection flaw in which external input reaches SQL query construction without reliable separation between data and query syntax. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command, with CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component describing the broader injection pattern. The insecure design allows a request parameter to influence database command behavior beyond its intended identifier value.

Potential impact

  • An attacker may retrieve unauthorized database information
  • Existing menu or application records could be altered or deleted
  • Database integrity and application availability could be affected
  • Credentials or other sensitive records may be exposed
  • The application could be used as a foothold for further compromise, depending on database permissions

General mitigation guidance

Mitigation generally focuses on ensuring that request values cannot alter SQL command structure.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations
  • Apply strict allowlist validation for identifiers and expected data types
  • Enforce authorization checks for administrative actions on the server side
  • Limit the database account to only the permissions required by the application
  • Avoid exposing administrative endpoints unnecessarily and apply secure session controls
  • Return generic database errors so query details are not disclosed

These controls reduce input trust and limit the consequences of an injection flaw.

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag string concatenation or interpolation in SQL queries
  • Code review checks for request parameters passed directly to database APIs
  • Dynamic testing of administrative endpoints with malformed and boundary-case identifiers
  • Web application firewall or API policy rules that monitor suspicious database-oriented input
  • Database audit logging for unexpected queries, record access, or deletion patterns

Automated security review tools may help identify unsafe query construction, but findings should be validated against the application's data-access layer.

Sources

SourceLink
github.comgithub.com/jackkoz0512/cve/issues/1
vuldb.comvuldb.com/cve/CVE-2026-76050
vuldb.comvuldb.com/submit/878241
vuldb.comvuldb.com/vuln/391951
vuldb.comvuldb.com/vuln/391951/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes, the affected endpoint is described as remotely reachable. Practical exploitability still depends on network exposure, authentication, and authorization controls.

Not necessarily. The required access depends on how the endpoint is protected; any missing or weak authorization would increase exposure.

Use parameterized database queries, validate the identifier as the expected type, and enforce server-side authorization before performing the deletion.

Combine secure database APIs with code review, static analysis, endpoint-level authorization testing, least-privilege database accounts, and monitoring for anomalous query activity.

Find out what's already
exploitable in your codebase.