dbcve.org
Simple Pizza Ordering SystemApplication · Carmelo

CVE-2025-6938

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-01
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 rated as critical. This issue affects some unknown processing of the file /editcus.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated 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 Simple Pizza Ordering System 1.0 application allows remote attackers to inject malicious SQL statements via the 'ID' parameter in /editcus.php. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or complete system compromise.

MitigationReplace dynamic SQL queries in editcus.php with prepared statements/parameterized queries to properly sanitize the ID parameter input, or implement input validation and escaping mechanisms before executing 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. Identify the Simple Pizza Ordering System version
    Locate the application files and check for version identifiers in source files, readme, or configuration. Common locations include version.php, about.php, or the main index file.
    Affected if The installed version matches 1.0 exactly.
  2. Verify the vulnerable script exists
    Check for the presence of /editcus.php in the web root directory of the application.
    Affected if The file editcus.php exists in the application directory.
  3. Inspect the editcus.php source code
    Open editcus.php and examine how the ID parameter is handled in database queries. Look for direct inclusion of $_GET or $_POST['ID'] in SQL statements without prepared statements or escaping functions.
    Affected if The ID parameter is used directly in SQL queries without parameterized queries, input sanitization, or escaping.
  4. Confirm the application is web-accessible
    Verify the web server is running and the application is accessible over HTTP/HTTPS. The SQL injection requires the vulnerable endpoint to be reachable.
    Affected if The application is running and editcus.php is accessible via web requests.
  5. Test the ID parameter for injection susceptibility
    Send a crafted request to editcus.php with the ID parameter (e.g., ID=1' OR '1'='1) and observe if the application returns database errors or unexpected behavior indicating unsanitized input is being executed.
    Affected if The application responds with SQL errors or exhibits behavior indicating the ID parameter is not being properly sanitized before use in database queries.

The environment is affected if running Simple Pizza Ordering System version 1.0 with the editcus.php file present and the ID parameter handled unsafely 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 in editcus.php with prepared statements/parameterized queries to properly sanitize the ID parameter input, or implement input validation and escaping mechanisms before executing database queries.

Fix this in Simple Pizza Ordering System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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