Five Star Restaurant MenuWordPress extension · Fivestarplugins
CVE-2023-34017
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 FiveStarPlugins Five Star Restaurant Reservations plugin <= 2.6.7 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 · moderate confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the Five Star Restaurant Reservations WordPress plugin affecting versions 2.6.7 and below, allowing remote attackers to inject malicious JavaScript through unsanitized user input that gets reflected back in HTTP responses.
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
Five Star Restaurant MenuWordPress extension
<= 2.6.7CVSS 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.
-
Confirm plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Five Star Restaurant Menu' or 'Five Star Restaurant Reservations' in the list. Note whether it is installed and active.Affected if The plugin is installed and active on the WordPress site.
-
Identify installed versionIn the plugins list, click on the plugin to view details, or check the plugin header in /wp-content/plugins/fivestarplugins-five-star-restaurant-menu/ folder. Compare the version number to 2.6.7.Affected if The installed version is 2.6.7 or lower.
-
Verify unauthenticated access vectorConfirm the plugin exposes any public-facing pages or endpoints that accept user input without authentication. This typically includes reservation forms or menu display pages accessible to non-logged-in users.Affected if Public-facing input forms or endpoints are accessible without login.
-
Check for XSS indicators in HTTP trafficReview server access logs for unusual query parameters in requests to the plugin pages. Look for patterns containing script tags, javascript:, or event handlers in the URL query strings.Affected if Suspicious XSS payloads appear in server logs targeting plugin endpoints.
A site is affected if it runs the Five Star Restaurant Menu plugin at version 2.6.7 or lower and has public-facing pages that accept unauthenticated user input.
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.
From vendor dataUpdate the plugin to the latest version immediately. As a temporary measure, disable the plugin if an update is unavailable. Implement Web Application Firewall (WAF) rules as defense-in-depth.
Fix this in Five Star Restaurant Menu
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34017 — 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-34017 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