# CVE-2026-116603: SourceCodester Online Food Ordering System add_food.php unrestricted upload


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-2rxc-43r4-h8r7

## What is CVE-2026-116603?

CVE-2026-116603 is a medium-severity vulnerability in SourceCodester Online Food Ordering System, published on 26 Oct 2026. 

### Official description

A flaw has been found in SourceCodester Online Food Ordering System 1.0. Impacted is an unknown function of the file admin/add_food.php. Executing a manipulation of the argument image can lead to unrestricted upload. The attack may be performed from remote. The exploit has been published and may be used.

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

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


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

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

## Is CVE-2026-116603 being exploited?

There is no known exploitation of CVE-2026-116603 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116603 is a medium-severity vulnerability in SourceCodester Online Food Ordering System, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116603 in the wild and no public exploit code.

Affected product: SourceCodester Online 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-116603/ (Markdown: https://insights.sbomify.com/CVE-2026-116603/index.md)
```

## Sources

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

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