/

CVE-2026-78247

Severity:

HIGH RISK

(7.3)

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

CVE-2026-78247

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Unauthorized database access or 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 high-severity SQL injection vulnerability affects the administrative order-confirmation endpoint in SourceCodester Simple Online Food Ordering System 1.0. A remote attacker may manipulate the order ID parameter to alter database queries when the endpoint is reachable and input is not safely handled.

Affected context

The vulnerability occurs in the application's administrative AJAX processing for order confirmation at /fos/admin/ajax.php?action=confirm_order. It becomes risky when the endpoint is remotely reachable, accepts attacker-controlled values in the ID argument, and incorporates those values into database queries without effective parameterization or equivalent neutralization.

Exploit preconditions

  • Attack surface: Remotely accessible web application endpoint
  • Required access: Network access to the affected application; authentication requirements may depend on deployment controls
  • Trigger point: Processing the ID argument during order confirmation
  • Why exploitation is possible: Attacker-controlled input may influence SQL query structure when the application does not use safe query parameterization

Why this happens

The underlying bug is improper neutralization of SQL metacharacters in externally supplied input. When the order ID is combined with a database query as executable SQL rather than being bound as data, an attacker may influence query interpretation. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and broadly relates to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component.

Potential impact

  • An attacker may read unauthorized database records
  • An attacker could modify or delete application data
  • Database integrity and order-processing workflows may be disrupted
  • Sensitive information may be exposed
  • Application availability could be affected

General mitigation guidance

Mitigation generally focuses on ensuring that database operations treat request values strictly as data.

Common defensive patterns include:

  • Use parameterized queries or prepared statements by default
  • Apply server-side allowlist validation for identifiers such as order IDs
  • Avoid constructing SQL statements through string concatenation
  • Use database accounts with only the permissions required by the application
  • Keep administrative endpoints behind appropriate authentication and authorization controls
  • Return generic database errors so query details are not disclosed
  • Use secure data-access abstractions that make unsafe query construction difficult

How teams detect issues like this

Organizations can look for SQL injection risks through:

  • Static analysis rules identifying string concatenation or interpolation in database queries
  • Code review checks for request parameters passed directly into SQL execution APIs
  • Testing that verifies parameterized queries and rejects malformed identifier input
  • Web application firewall policies monitoring suspicious query-manipulation patterns
  • Database and application logs showing abnormal query errors, unusual data access, or unexpected administrative activity
  • Automated security review tools that flag unsafe data-access patterns during development

Sources

SourceLink
github.comgithub.com/huliangjia/cve/issues/1
vuldb.comvuldb.com/cve/CVE-2026-78247
vuldb.comvuldb.com/submit/886181
vuldb.comvuldb.com/vuln/394597
vuldb.comvuldb.com/vuln/394597/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The affected endpoint can be reached remotely, although network exposure, authentication, and authorization controls may limit who can interact with it.

The attacker needs network access to the application and a way to submit input to the order-confirmation endpoint. Whether authentication is required depends on the deployment's access controls.

Use prepared statements or parameterized queries for every database operation, validate identifiers on the server, and avoid building SQL with untrusted string values.

Combine secure data-access APIs with least-privilege database accounts, focused code review, static analysis, endpoint authorization, and monitoring for abnormal database activity.

Find out what's already
exploitable in your codebase.