# CVE-2026-123988: SililaWijesinghe Food Ordering System admin exposure of information through directory listing


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-673h-mfmj-7wjm

## What is CVE-2026-123988?

CVE-2026-123988 is a medium-severity vulnerability in SililaWijesinghe Food Ordering System, published on 7 Nov 2026. 

### Official description

A vulnerability has been found in SililaWijesinghe Food Ordering System up to ba314e897e3365600461e5ea59432e39ceaa0fa5. This issue affects some unknown processing of the file /Food-Ordering-System/admin/. Such manipulation leads to exposure of information through directory listing. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-548 (Exposure of Information Through Directory Listing)

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


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

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

## Is CVE-2026-123988 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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