dbcve.org
Simple Pizza Ordering SystemApplication · Carmelo

CVE-2025-6364

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 has been found in code-projects Simple Pizza Ordering System 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /adduser-exec.php. The manipulation of the argument Username leads to sql injection. The attack can be launched 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

SQL injection vulnerability in the /adduser-exec.php file of Simple Pizza Ordering System 1.0 allows remote attackers to inject malicious SQL queries via the Username parameter. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries, potentially gaining unauthorized access to sensitive data or executing arbitrary commands on the database.

MitigationImplement prepared statements/parameterized queries for all database operations involving user input, particularly the Username parameter in adduser-exec.php. Additionally, apply input validation and least-privilege database user permissions to limit the impact of any successful SQL injection.

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 web root directories for the application files, specifically looking for adduser-exec.php or other PHP files that contain 'Simple Pizza Ordering System' in their content. Common paths include /var/www/html, /www, or C:\inetpub\wwwroot.
    Affected if The application is installed and the vulnerable file adduser-exec.php exists in the web-accessible directory.
  2. Verify the application version
    Examine the application for a version indicator such as a README file, version comment in PHP files, or the login/admin page footer. Compare the found version to the affected version 1.0.
    Affected if The installed version is exactly 1.0.
  3. Inspect adduser-exec.php for proper input handling
    Open adduser-exec.php in a text editor and locate the code handling the Username parameter. Search for the use of prepared statements, parameterized queries, or functions like mysqli_prepare/PDO::prepare. Also check for sanitization functions like mysqli_real_escape_string or htmlspecialchars applied to the Username variable.
    Affected if The code directly incorporates the Username parameter into SQL queries without using prepared statements or escaping functions.
  4. Check if the user registration endpoint is accessible
    Attempt to access the user registration page or adduser-exec.php directly via HTTP/HTTPS to confirm the endpoint is reachable. Also verify that the web server is running and the application is publicly or internally accessible.
    Affected if The adduser-exec.php endpoint is accessible and the Username parameter can be submitted via HTTP POST or GET requests.
  5. Review database user privileges
    If you have database access, examine the database user configured in the application configuration file (often config.php or db_connect.php) to determine if it has excessive privileges beyond what the application requires.
    Affected if The database user has privileges beyond SELECT, INSERT, UPDATE, and DELETE on the application database, such as DROP, CREATE, or file access permissions.

A user is affected if Simple Pizza Ordering System version 1.0 is installed, the adduser-exec.php file exists, and the Username parameter is handled without prepared statements or input sanitization in the code.

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

Implement prepared statements/parameterized queries for all database operations involving user input, particularly the Username parameter in adduser-exec.php. Additionally, apply input validation and least-privilege database user permissions to limit the impact of any successful SQL injection.

Fix this in Simple Pizza Ordering System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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