CVE-2023-0257
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 was found in SourceCodester Online Food Ordering System 2.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /fos/admin/index.php?page=menu of the component Menu Form. The manipulation of the argument Image with the input <?php system($_GET['c']); ?> leads to unrestricted upload. The attack can be launched remotely. The identifier VDB-218185 was assigned to this vulnerability.
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 confidenceThe application fails to validate file types when uploading images in the Menu Form at /fos/admin/index.php?page=menu. An attacker can upload a PHP file containing a web shell (<?php system($_GET['c']); ?>) that enables remote code execution on the server.
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= 2.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.
-
Identify the application and versionLocate application files or check the admin panel for version information. Oretnom23 Online Food Ordering System v2.0 typically has version indicators in source files, changelogs, or admin dashboard About sections.Affected if The installed version is Oretnom23 Online Food Ordering System version 2.0
-
Verify the vulnerable upload endpoint existsCheck if the file /fos/admin/index.php exists and responds to the parameter page=menu. Access the admin panel and navigate to the Menu Form upload functionality.Affected if The endpoint /fos/admin/index.php?page=menu is accessible and displays an image upload form
-
Inspect upload form file type validationExamine the HTML form at the Menu page for input type=file elements, then check the server-side script handling the upload (typically in the same directory or an includes folder) for MIME type, extension, or magic bytes validation logic.Affected if The upload handler lacks or has weak file type validation (no magic byte checks, no strict extension whitelist, or no MIME type verification)
-
Verify uploaded files are web-accessibleLocate the upload directory configuration (check the PHP handling the upload for the destination path) and confirm whether uploaded files are stored within the web document root.Affected if Uploaded files are stored in a web-accessible directory (such as /fos/assets/uploads/ or similar) and PHP execution is not disabled on that directory
If the system is Oretnom23 Online Food Ordering System v2.0 with the Menu Form upload endpoint present and lacking proper file type validation, an attacker can upload and execute PHP files, making the environment affected by CVE-2023-0257.
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 (magic bytes, MIME type, extension whitelist) before allowing uploads; store uploaded files outside the webroot or rename them and disable PHP execution in the upload directory.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0257 — 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-0257 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