dbcve.org
Online Pizza Ordering SystemApplication · Oretnom23

CVE-2023-5423

CRITICAL · 9.8 CVSS v3.1 Published 2023-10-05
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
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 SourceCodester Online Pizza Ordering System 1.0 and classified as critical. This vulnerability affects unknown code of the file /admin/ajax.php?action=confirm_order. The manipulation of the argument id leads to sql injection. The attack can be initiated remotely. The identifier of this vulnerability is VDB-241384.

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 SourceCodester Online Pizza Ordering System 1.0 allows remote attackers to inject malicious SQL queries via the 'id' parameter in the /admin/ajax.php?action=confirm_order endpoint. The application fails to properly sanitize user input before using it in database queries.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for the 'id' parameter in the confirm_order function, and implement proper input validation. Restrict admin access to authenticated users as a defense-in-depth measure.

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
Online 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 the installed application and version
    Locate and examine the application files or footer/admin panel for version information. Check for files like version.php, README, or the main application entry point to identify if the system is SourceCodester/Oretnom23 Online Pizza Ordering System version 1.0.
    Affected if The installed application is SourceCodester/Oretnom23 Online Pizza Ordering System version 1.0.
  2. Locate the affected endpoint file
    Search for the file /admin/ajax.php in the web application directory structure. Verify its existence and examine its contents.
    Affected if The file admin/ajax.php exists in the web root.
  3. Inspect the confirm_order function
    Open admin/ajax.php and locate the function or code block handling 'action=confirm_order'. Examine how the 'id' parameter is processed and whether it is used directly in SQL queries without sanitization or parameterization.
    Affected if The 'id' parameter from the request is concatenated directly into SQL queries without using prepared statements or escaping functions.
  4. Verify database query construction for the id parameter
    Trace the flow of the 'id' parameter from the HTTP request through the confirm_order function to the database query. Look for any use of string concatenation, string interpolation, or direct insertion of the 'id' value into SQL statements.
    Affected if The 'id' parameter is used in SQL queries without bound parameters, such as through $sql = "SELECT... WHERE id = " . $_GET['id'] or similar patterns.
  5. Check admin access control on the endpoint
    Determine if the /admin/ajax.php?action=confirm_order endpoint enforces authentication or authorization before processing requests. Review session handling and access control logic in the admin directory.
    Affected if The endpoint is accessible without authentication or with insufficient access controls, allowing unauthenticated SQL injection attempts.

If the system is SourceCodester/Oretnom23 Online Pizza Ordering System version 1.0 and the admin/ajax.php file contains the vulnerable confirm_order function that uses the 'id' parameter directly in SQL queries without sanitization or prepared statements, the environment is affected.

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 with parameterized queries (prepared statements) for the 'id' parameter in the confirm_order function, and implement proper input validation. Restrict admin access to authenticated users as a defense-in-depth measure.

Fix this in Online Pizza Ordering System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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