dbcve.org
Simple Pizza Ordering SystemApplication · Carmelo

CVE-2025-6358

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-20
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
A vulnerability was found in code-projects Simple Pizza Ordering System 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /saveorder.php. The manipulation of the argument ID leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

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 · high confidence

SQL injection vulnerability in the ID parameter of /saveorder.php in Simple Pizza Ordering System 1.0 allows remote attackers to inject arbitrary SQL commands via unsanitized user input.

MitigationReplace dynamic SQL queries in saveorder.php with parameterized queries/prepared statements, or sanitize and validate the ID parameter before using it in database queries.

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 Pizza Ordering 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. Confirm Simple Pizza Ordering System is installed
    Locate the web application directory and identify if it contains the Simple Pizza Ordering System (search for files like index.php, saveorder.php, or version indicators such as readme.txt, CHANGELOG.txt, or a version constant in source files)
    Affected if The application files for Simple Pizza Ordering System are found on the system
  2. Verify the application version is 1.0
    Search for version indicators in the application source code (look for a version variable in config files, readme.txt, or the main PHP files) and compare against the affected version 1.0
    Affected if The installed version is exactly 1.0 (no patches applied)
  3. Confirm saveorder.php exists and is accessible
    Locate the saveorder.php file within the web application directory structure and verify it is accessible via the web server (the CVE specifies this file as the vulnerable endpoint)
    Affected if The file /saveorder.php exists in the web-accessible directory
  4. Verify the ID parameter accepts user input without authentication
    Examine the saveorder.php source code to determine if the ID parameter is processed directly from user request without authentication checks (the CVE indicates the ID parameter is vulnerable to SQL injection)
    Affected if The ID parameter in saveorder.php is processed without authentication and used in database queries
  5. Check for dynamic SQL query usage
    Inspect saveorder.php source code for dynamic SQL construction patterns (string concatenation or interpolation of user input into SQL queries without prepared statements or parameter binding)
    Affected if The application constructs SQL queries dynamically using the ID parameter without parameterized queries

The system is affected if Simple Pizza Ordering System version 1.0 is installed with saveorder.php accessible and using dynamic SQL queries with the unauthenticated ID parameter.

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 in saveorder.php with parameterized queries/prepared statements, or sanitize and validate the ID parameter before using it in database queries.

Fix this in Simple Pizza Ordering System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6358 — 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-2025-6358 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