CVE-2022-29650
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 Search parameter at /online-food-order/food-search.php.
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 Search parameter of food-search.php in Online Food Ordering System v1.0. The search input is not properly sanitized before being used in SQL queries, allowing attackers to manipulate database queries through specially crafted input.
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 application installationLocate the web root directory and identify if the Online Food Ordering System (Oretnom23) is installed. Look for application files, readme files, or version indicators to confirm the product name and version 1.0.Affected if The system is running Oretnom23 Online Food Ordering System version 1.0
-
Verify the vulnerable file existsCheck the web server document root for the file food-search.php. Common paths may include /food-search.php or /includes/food-search.php within the application directory.Affected if food-search.php exists in the application directory structure
-
Check if search functionality is accessibleAttempt to access the food-search.php page via HTTP GET request to the web server. Observe if the page loads and accepts a 'search' parameter in the URL query string.Affected if The page loads and accepts a 'search' parameter input field or URL parameter
-
Inspect the code for dynamic SQL constructionOpen food-search.php in a text editor or via command line and locate code that constructs SQL queries using the search parameter directly, such as "SELECT * FROM ... WHERE ... LIKE '%" . $_GET['search'] . "%'", without using prepared statements or parameter binding.Affected if The code builds SQL queries by directly concatenating user input from the search parameter into the query string
-
Review web server logs for suspicious SQL patternsExamine access logs (typically in /var/log/apache2/ or /var/log/nginx/) for the food-search.php endpoint. Look for SQL injection payloads in the search parameter, such as quotes, UNION SELECT, or OR 1=1 patterns.Affected if Logs show SQL injection attempts against the search parameter or evidence of successful injection-based access
A system is affected if it runs Oretnom23 Online Food Ordering System v1.0 with the food-search.php file present and the search functionality enabled, where the code directly incorporates the search parameter into SQL queries without prepared statements.
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 parameterized queries (prepared statements) in food-search.php, implement proper input validation and sanitization for all user-supplied search parameters, and conduct thorough testing to confirm the injection vector is eliminated.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29650 — 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-29650 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