# CVE-2026-114700: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Gloriafood Restaurant Menu – Food Orde


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-7vpq-7634-pfcf

## What is CVE-2026-114700?

CVE-2026-114700 is a medium-severity vulnerability in Gloriafood Restaurant Menu – Food Ordering System – Table Reservation, published on 22 Oct 2026. 

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Gloriafood Restaurant Menu – Food Ordering System – Table Reservation menu-ordering-reservations allows Stored XSS.This issue affects Restaurant Menu – Food Ordering System – Table Reservation: from n/a through 2.4.4.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-114700 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114700 is a medium-severity vulnerability in Gloriafood Restaurant Menu – Food Ordering System – Table Reservation, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114700 in the wild and no public exploit code.

Affected product: Gloriafood Restaurant Menu – Food Ordering System – Table Reservation. 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-114700/ (Markdown: https://insights.sbomify.com/CVE-2026-114700/index.md)
```

## Sources

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

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