CVE-2022-29651
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 · uneditedAn arbitrary file upload vulnerability in the Select Image function of Online Food Ordering System v1.0 allows attackers to execute arbitrary code via a crafted PHP file.
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 · moderate confidenceAn authenticated arbitrary file upload vulnerability exists in the Select Image function of Online Food Ordering System v1.0. The application fails to properly validate uploaded files, allowing attackers to upload malicious PHP scripts that can be executed on the server to achieve arbitrary code execution.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify the application versionLocate the version information for the Online Food Ordering System. This is typically found in the application header, footer, admin dashboard 'About' page, or in a version.php/readme.txt file within the web root. Compare the installed version to the affected version (1.0).Affected if The application is Oretnom23 Online Food Ordering System version 1.0
-
Verify the Select Image upload functionality existsAccess the application's admin panel or user interface and navigate to any feature that includes a file upload or image selection function. Check if the 'Select Image' functionality is present and accessible (typically in product/menu item management pages).Affected if The Select Image/file upload functionality is enabled and accessible to authenticated users
-
Check upload directory web accessibilityExamine the web server configuration and the application's upload directory. Determine if uploaded files are stored within the web root and can be accessed directly via a URL (e.g., /uploads/ or /images/ directory).Affected if Uploaded files are stored in a web-accessible directory and can be executed by requesting the file URL directly
-
Verify file execution restrictionsAttempt to upload a harmless test file (such as a plain text file with a .txt extension) through the Select Image function, then access the file via web browser to confirm whether the server executes or serves the file content.Affected if Uploaded files are served with executable permissions or the server interprets them as PHP/scripts, allowing potential code execution
A user is affected if they are running Oretnom23 Online Food Ordering System version 1.0 with the Select Image upload feature enabled and the upload directory accessible via the web, allowing uploaded files to be executed.
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 dataImplement strict file type validation using both MIME type and extension whitelist checks, store uploaded files outside the web root or in a non-executable directory, and rename files upon upload to prevent direct script execution.
- 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-29651 — 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-29651 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