dbcve.org
Simple Food Order SystemApplication · Carmelo

CVE-2026-26713

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
code-projects Simple Food Order System v1.0 is vulnerable to SQL Injection in /food/routers/cancel-order.php.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL Injection vulnerability in /food/routers/cancel-order.php of the Simple Food Order System v1.0 allows unauthenticated attackers to inject malicious SQL queries via user input (likely order ID parameters), potentially enabling unauthorized data access, modification, or complete database compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in cancel-order.php and all related database interactions; implement input validation and least-privilege database accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Simple Food Order SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed application version
    Locate any version identifier files (such as readme.txt, version.php, or admin dashboard version info) in the web application root directory. Search for 'Simple Food Order System' or 'Carmelo' branding in source files or footer pages.
    Affected if The installed version matches 1.0 of the Simple Food Order System by Carmelo.
  2. Locate the vulnerable cancel-order.php file
    Search the web application directory tree for a file named cancel-order.php. Common paths include the root directory or a subdirectory like /admin/, /pages/, or /functions/.
    Affected if The file cancel-order.php exists in the application structure.
  3. Verify the cancel-order.php endpoint is web-accessible
    Attempt to access the cancel-order.php file via HTTP/HTTPS request (for example: https://yourdomain.com/cancel-order.php or the appropriate subdirectory path). Check for a response rather than a 404 error.
    Affected if The cancel-order.php file is served by the web server and responds to requests.
  4. Confirm database connectivity is active
    Check if the application has a functional database connection by attempting to use any order-related feature, or by examining configuration files (such as config.php, db.php, or similar) for active database credentials.
    Affected if The application is configured with a working database connection and is operational.
  5. Inspect SQL query handling in cancel-order.php
    Open cancel-order.php in a text editor and examine any SQL queries within the file. Look for query construction that uses user-supplied input (such as $_GET, $_POST, or $_REQUEST parameters) directly without using prepared statements, parameter binding, or input sanitization functions.
    Affected if The file contains SQL queries that incorporate user input without parameterized queries or proper sanitization.

You are affected if you are running Simple Food Order System version 1.0 with the cancel-order.php file present, accessible, and connected to an operational database where the code uses unsanitized user input in SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in cancel-order.php and all related database interactions; implement input validation and least-privilege database accounts.

Fix this in Simple Food Order System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26713 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data