CVE-2022-36759
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 · uneditedOnline Food Ordering System v1.0 was discovered to contain a SQL injection vulnerability via the component /dishes.php?res_id=.
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 confidenceSQL injection vulnerability in Online Food Ordering System v1.0 allows remote attackers to inject malicious SQL queries via the res_id parameter in /dishes.php. The lack of proper input sanitization or use of parameterized queries enables unauthenticated attackers to manipulate database queries.
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.
-
Verify the Online Food Ordering System is installedCheck your web server for the presence of the Oretnom23 Online Food Ordering System v1.0. Look for directories containing files like dishes.php, index.php, or admin/ folder. Search for application files with version markers or readme files indicating version 1.0.Affected if The application directory exists and is the Oretnom23 Online Food Ordering System version 1.0
-
Locate the dishes.php fileSearch the web root for the file dishes.php. This is the vulnerable file mentioned in the CVE. Common paths may include /dishes.php or /food/dishes.php.Affected if The file dishes.php exists in the web-accessible directory
-
Inspect the res_id parameter handling in dishes.phpOpen dishes.php and examine the code that handles the res_id GET parameter. Look for SQL queries that directly use $_GET['res_id'] or $_REQUEST['res_id'] without sanitization or parameterized queries.Affected if The code uses the res_id parameter directly in SQL queries without prepared statements, binding parameters, or input validation functions like mysqli_real_escape_string or htmlspecialchars
-
Test if the res_id parameter is acceptedMake a test request to dishes.php with a res_id parameter value, such as res_id=1. Check if the application responds and returns data based on this parameter.Affected if The application accepts the res_id parameter and returns database-driven content without requiring authentication
-
Check for absence of parameterized queriesIn dishes.php, search for SQL query patterns (SELECT, INSERT, UPDATE, DELETE) and verify if they use mysqli_prepare, PDO::prepare, or similar parameterized query methods. If queries concatenate or embed the res_id variable directly into SQL strings, the vulnerability is present.Affected if SQL queries in dishes.php concatenate user input directly into query strings rather than using parameterized queries or prepared statements
You are affected if the Oretnom23 Online Food Ordering System v1.0 is running and the dishes.php file contains SQL queries that use the res_id parameter without parameterized queries or input sanitization.
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 with prepared statements/parameterized queries in dishes.php, apply input validation on the res_id parameter, and conduct a broader audit of the application for similar SQL injection vulnerabilities.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36759 — 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-2022-36759 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