Restaurant Menu Food Ordering System Table ReservationWordPress extension · Oracle
CVE-2023-32516
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in GloriaFood Restaurant Menu – Food Ordering System – Table Reservation plugin <= 2.3.6 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the GloriaFood Restaurant Menu – Food Ordering System – Table Reservation plugin versions 2.3.6 and below allows attackers to inject malicious JavaScript via unsanitized user input that gets reflected in the web page response.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Restaurant Menu Food Ordering System Table ReservationWordPress extension
<= 2.3.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if the GloriaFood plugin is installedAccess your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'GloriaFood Restaurant Menu - Food Ordering System - Table Reservation' in the list of active or installed plugins.Affected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn the WordPress Plugins page, click on the plugin name or view the version number displayed under the plugin title. Compare this version number against the affected range of 2.3.6 and below.Affected if The installed version is 2.3.6 or any lower version number
-
Determine if the vulnerable endpoint is accessibleExamine your web server logs or use a network proxy to identify any incoming requests targeting the GloriaFood plugin's front-end pages. The vulnerability is a reflected XSS, so it would be triggered via a specific URL parameter.Affected if Requests to the plugin's public-facing pages are being served without additional access controls
-
Verify the attack vector conditionSince this is a reflected XSS, test a benign parameter injection on the plugin's public order or reservation page. Use a safe test string like '<script>alert(1)</script>' in URL parameters and observe if the input is reflected unescaped in the response.Affected if The test string appears literally in the page response without HTML encoding
You are affected if the GloriaFood plugin version is 2.3.6 or lower and the plugin's public ordering or reservation pages are accessible, allowing unsanitized user input to be reflected in the response.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to the latest version immediately and implement proper input sanitization and output encoding on all user-supplied parameters.
Latest version available in WordPress plugin repository (above 2.3.6)
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the GloriaFood Restaurant Menu – Food Ordering System – Table Reservation plugin
- Check the current installed version (ensure it is <= 2.3.6)
- Update the plugin to the latest available version from the WordPress plugin repository
- Verify the update was successful and the new version is running
- Test that the reflected XSS vulnerability is no longer exploitable in the application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Restaurant Menu Food Ordering System Table Reservation
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32516 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32516 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data