# CVE-2026-116602: SourceCodester Online Food Ordering System delete.php unlink path traversal


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/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-p4vm-43g4-5hh7

## What is CVE-2026-116602?

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

### Official description

A vulnerability was detected in SourceCodester Online Food Ordering System 1.0. This issue affects the function unlink of the file admin/delete.php. Performing a manipulation of the argument image_name results in path traversal. The attack is possible to be carried out remotely. The exploit is now public and may be used.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-116602 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116602 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-116602 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-116602/ (Markdown: https://insights.sbomify.com/CVE-2026-116602/index.md)
```

## Sources

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

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