dbcve.org
Simple Pizza Ordering SystemApplication · Carmelo

CVE-2025-6356

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 and classified as critical. This issue affects some unknown processing of the file /addmem.php. The manipulation 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

A critical SQL injection vulnerability exists in the /addmem.php file of the Simple Pizza Ordering System 1.0. The attack vector is remote and requires no authentication, allowing attackers to manipulate SQL queries through unsanitized input. With a CVSS score of 9.8, successful exploitation can lead to full database compromise, including potential data exfiltration or remote code execution via database features.

MitigationImmediately restrict network access to the application if possible. As an immediate compensating control, implement a WAF rule to block SQL injection patterns in requests to /addmem.php. For permanent remediation, obtain the source code and refactor the affected code to use parameterized queries (prepared statements) instead of concatenating user input directly into SQL strings.

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. Locate the Simple Pizza Ordering System installation
    Search the system for files or directories containing 'pizza' or 'SimplePizza' in the name. Check web server document roots (e.g., /var/www/html, /htdocs, C:\inetpub\wwwroot) for a folder containing the application.
    Affected if The application is found in the system
  2. Verify the exact version installed
    Look for a version file, README, or any file within the application directory that displays the version number. Common locations include version.php, readme.txt, or the main index page source.
    Affected if The installed version is exactly 1.0 (Carmelo Simple Pizza Ordering System)
  3. Confirm the vulnerable file exists
    Locate the addmem.php file within the application directory. Check for the presence of /addmem.php or a path like /includes/addmem.php, /pages/addmem.php, or similar within the application structure.
    Affected if The file addmem.php exists in the application installation
  4. Verify network accessibility of the vulnerable endpoint
    If the application is web-facing, test if the /addmem.php endpoint responds by making an HTTP request to the URL (e.g., http://[target]/addmem.php). A 200 or 400 response indicates the endpoint is reachable.
    Affected if The addmem.php endpoint is accessible over the network (HTTP/HTTPS)
  5. Check if the application handles user input in addmem.php
    Examine the addmem.php source code for SQL query handling. Look for database connection calls (mysqli_query, mysql_query, $conn->query) and whether user-supplied parameters are concatenated directly into SQL strings without using prepared statements or parameter binding.
    Affected if The code directly concatenates user input into SQL queries without sanitization or parameterized queries

The environment is affected if the Carmelo Simple Pizza Ordering System version 1.0 is installed, the addmem.php file exists, and it is accessible over the network with unsanitized SQL query handling.

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

Immediately restrict network access to the application if possible. As an immediate compensating control, implement a WAF rule to block SQL injection patterns in requests to /addmem.php. For permanent remediation, obtain the source code and refactor the affected code to use parameterized queries (prepared statements) instead of concatenating user input directly into SQL strings.

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