# CVE-2026-127283: SourceCodester Food Ordering System Admin Image update_food.php unrestricted upload


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-6f6q-94cr-hm6f

## What is CVE-2026-127283?

CVE-2026-127283 is a medium-severity vulnerability in SourceCodester Food Ordering System, published on 13 Nov 2026. 

### Official description

A vulnerability was identified in SourceCodester Food Ordering System 1.0. Affected by this issue is some unknown functionality of the file admin/update_food.php of the component Admin Image Handler. Such manipulation of the argument cmd leads to unrestricted upload. The attack may be performed from remote. The exploit is publicly available and might be used.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-127283?

It affects 1 product.


Products: Sourcecodester Food Ordering System.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:sourcecodester:food_ordering_system:*:*:*:*:*:*:*:*` from 1.0 up to 1.0

## How do I fix CVE-2026-127283?

No fix has been published for CVE-2026-127283 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-127283 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-127283 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127283 and fix it if it is affected.

What it is: CVE-2026-127283 is a medium-severity vulnerability in SourceCodester Food Ordering System, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-127283 exists.

Affected product: SourceCodester Food Ordering System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127283/ (Markdown: https://insights.sbomify.com/CVE-2026-127283/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127283
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127283
- OSV: https://osv.dev/vulnerability/CVE-2026-127283

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127283/
Summaries are generated and may contain mistakes; the official description above is the record.
