/

CVE-2026-78197

Severity:

HIGH RISK

(7.3)

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

CVE-2026-78197

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise and unauthorized data access

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 Username handling in the Simple Online Food Ordering System's administrative AJAX endpoint. A remote attacker may be able to manipulate database queries, potentially exposing, changing, or disrupting application data when the input reaches an unsafe SQL execution path.

Affected context

The vulnerability occurs in the administrative endpoint /fos/admin/ajax.php?action=save_user of Simple Online Food Ordering System 1.0. Risk depends on whether the endpoint is reachable by an attacker and whether the Username value is incorporated into database operations without adequate parameterization or validation. Public exploit availability may increase exposure for deployments that leave the endpoint accessible.

Exploit preconditions

  • Attack surface: Remotely reachable administrative AJAX endpoint
  • Required access: Network access to the endpoint; authentication requirements depend on the deployment's access controls
  • Trigger point: Processing the Username argument during user-save operations
  • Why exploitation is possible: User-controlled input may influence a database query without sufficient separation between data and SQL instructions

Why this happens

The underlying bug is an injection-prone database interaction in which externally supplied Username data can be interpreted as part of a SQL statement. This behavior maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and more broadly to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component. The insecure pattern occurs when application input is concatenated into SQL or otherwise reaches a query execution layer without parameterized handling.

Potential impact

  • An attacker may read sensitive records from the application's database.
  • An attacker could modify or delete user and ordering data.
  • Database credentials or other stored secrets may be exposed.
  • The application may experience data integrity loss or service disruption.
  • Compromised database access could enable further attacks against connected systems.

General mitigation guidance

Mitigation generally focuses on ensuring that user-controlled values remain data throughout database processing.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations.
  • Avoid constructing SQL statements through string concatenation.
  • Apply server-side validation with allowlisted formats appropriate for usernames.
  • Restrict database accounts to the minimum permissions required by the application.
  • Protect administrative endpoints with strong authentication, authorization, and network exposure controls.
  • Avoid returning detailed database errors to clients.
  • Treat client-side validation as supplementary rather than a trust boundary.

How teams detect issues like this

Organizations can look for SQL injection risks through:

  • Static analysis rules identifying string concatenation or interpolation in SQL execution paths.
  • Code review checks for unparameterized queries involving request parameters.
  • Dynamic testing of administrative endpoints using safe, non-destructive injection test cases.
  • Web application firewall or gateway policies that detect suspicious database metacharacter patterns, while recognizing that filtering is not a substitute for parameterization.
  • Monitoring for unusual query errors, unexpected database reads, and abnormal activity against user-management endpoints.
  • Automated security scanning and code-review tools that flag injection-prone data flows.

Sources

SourceLink
github.comgithub.com/wsx138/cve/issues/3
vuldb.comvuldb.com/cve/CVE-2026-78197
vuldb.comvuldb.com/submit/886034
vuldb.comvuldb.com/submit/886038
vuldb.comvuldb.com/vuln/394574
vuldb.comvuldb.com/vuln/394574/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes, the affected endpoint is reachable over the network when exposed by a deployment. Actual exploitability depends on routing, authentication, authorization, and other deployment controls.

The available description does not establish a specific authentication requirement. Access to the endpoint and any controls protecting it determine whether an unauthenticated or authenticated attacker can reach the vulnerable operation.

Use parameterized queries or prepared statements, validate input on the server, and ensure the database account has only necessary privileges.

Enforce secure database-access patterns in shared libraries and code review, scan request-to-query data flows, protect administrative interfaces, and monitor database and endpoint activity for anomalies.

Find out what's already
exploitable in your codebase.