dbcve.org
Simple Pizza Ordering SystemApplication · Carmelo

CVE-2025-6362

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, which was classified as critical, has been found in code-projects Simple Pizza Ordering System 1.0. This issue affects some unknown processing of the file /editpro.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotely.

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

The Simple Pizza Ordering System 1.0 contains a critical SQL injection vulnerability in /editpro.php. The ID parameter passed to this file is not properly sanitized or parameterized, allowing an attacker to inject arbitrary SQL commands. This can lead to unauthorized database access, data exfiltration, or potential remote code execution depending on database configuration.

MitigationImplement prepared statements/parameterized queries for all database operations, particularly for the ID parameter in /editpro.php. Additionally, apply input validation and output encoding to prevent similar injection flaws.

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 product and version
    Locate the Simple Pizza Ordering System installation and identify the exact version number. Check version files, about pages, or headers within the application.
    Affected if The installed version is Carmelo Simple Pizza Ordering System 1.0 exactly.
  2. Verify editpro.php exists
    Check for the presence of the file /editpro.php in the web root or application directory. Use file system inspection or HTTP requests to confirm accessibility.
    Affected if The file editpro.php exists and is accessible via the web server.
  3. Identify ID parameter usage
    Review the editpro.php source code and locate where the ID parameter is used in SQL queries. Search for SQL query strings containing $_GET, $_POST, or $_REQUEST with 'ID' or 'id'.
    Affected if The ID parameter is directly incorporated into SQL queries without visible sanitization or parameterized queries.
  4. Test for SQL injection
    Submit a crafted ID parameter value such as "1' OR '1'='1" or "1 AND 1=1" to the editpro.php endpoint via GET or POST, and observe the application response for SQL errors or unexpected behavior.
    Affected if The application returns database errors, behaves unexpectedly with boolean-based payloads, or displays data it should not.

A user is affected if they are running Simple Pizza Ordering System version 1.0 with the editpro.php file accessible and the ID parameter vulnerable to SQL injection.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations, particularly for the ID parameter in /editpro.php. Additionally, apply input validation and output encoding to prevent similar injection flaws.

Recommended fix Moderate confidence
  1. 1. Locate the file /editpro.php in the web root of the Simple Pizza Ordering System.
  2. 2. Open the file and identify the SQL query that incorporates the 'ID' parameter (e.g., SELECT ... WHERE ID = $_GET['ID']).
  3. 3. Replace the dynamic SQL with a prepared statement using MySQLi or PDO. Example with MySQLi: $stmt = $conn->prepare('SELECT * FROM your_table WHERE ID = ?'); $stmt->bind_param('i', $id);
  4. 4. Ensure the $id variable is cast to an integer (e.g., $id = (int)$_GET['ID']) before binding, or rely entirely on the parameter binding for type safety.
  5. 5. Remove any direct concatenation or interpolation of $_GET['ID'] into the query string.
  6. 6. Test the patched page by supplying both legitimate and crafted 'ID' values to confirm the SQL injection is blocked.
  7. 7. Deploy the corrected /editpro.php to the production environment and monitor for any runtime errors.
Caveat Migrating to prepared statements may require changes if the original code uses the deprecated mysql_* functions; ensure compatibility with the current PHP MySQL extension.

Generated from the published advisory — verify against the referenced sources before acting.

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-6362 — 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-6362 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