CVE-2023-0910
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 · uneditedA vulnerability has been found in SourceCodester Online Pizza Ordering System 1.0 and classified as critical. This vulnerability affects unknown code of the file view_prod.php of the component GET Parameter Handler. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The identifier of this vulnerability is VDB-221476.
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 confidenceA SQL injection vulnerability exists in the view_prod.php file of SourceCodester Online Pizza Ordering System 1.0. The ID GET parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. This is a critical unauthenticated remote code execution vector given the SQL injection can potentially be leveraged to extract data, escalate privileges, or potentially execute OS commands depending on database configuration.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the installed product and versionLocate the Online Pizza Ordering System installation directory and identify the version number. Check any version file, README, or about page within the application.Affected if The installed version is exactly 1.0 of the Online Pizza Ordering System
-
Locate the view_prod.php fileSearch for the file view_prod.php in the web application directory structure. This file is the vulnerable component.Affected if The file view_prod.php exists in the application root or within the source code
-
Examine the ID parameter handling in view_prod.phpOpen view_prod.php and inspect the code around line handling the 'ID' GET parameter. Look for SQL query construction that directly uses $_GET['ID'] or $_REQUEST['ID'] without sanitization or prepared statements.Affected if The code directly incorporates the ID GET parameter into a SQL query without using prepared statements, parameter binding, or input sanitization functions such as htmlspecialchars() or mysqli_real_escape_string()
-
Verify dynamic SQL query usageSearch for SQL query patterns like 'SELECT', 'INSERT', 'UPDATE', or 'DELETE' statements that concatenate the ID parameter directly into the query string.Affected if Dynamic SQL queries concatenate the ID parameter without parameterized binding, creating the injection vector
-
Check application accessibilityDetermine if the view_prod.php file is accessible via HTTP/HTTPS requests from the web. Attempt to access it through the browser or curl command.Affected if The vulnerable file is publicly accessible and the application is reachable over the network
A system is affected if it runs SourceCodester Online Pizza Ordering System version 1.0 with the view_prod.php file accessible and containing unsanitized ID parameter usage in dynamic SQL queries.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries in view_prod.php with prepared statements/parameterized queries to properly sanitize the ID parameter input. Conduct a full code audit of the application to identify and remediate additional SQL injection vulnerabilities in other files.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-0910 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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