Radar sectionsDatabase
Check my site
WordPress plugin

Five Star Restaurant Reservations <= 2.7.16 — Unauthenticated Payment Bypass via PHP Type Juggling in 'payment_id' Parameter

CVE-2026-6498Published · Updated

Action summary

Affected: ≤2.7.16Update to 2.7.17 or newer

All remediation steps
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-345 Insufficient Verification of Data Authenticity
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Five Star Restaurant Reservations – WordPress Booking Plugin restaurant-reservations

  1. Affected≤ 2.7.16
  2. Patched in2.7.17

Update to 2.7.17 or newer.

You are affected if you run ≤ 2.7.16. Version 2.7.17 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Five Star Restaurant Reservations – WordPress Booking Plugin.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.7.17, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Five Star Restaurant Reservations – WordPress Booking Plugin to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to davidfdzmorilla.

The Five Star Restaurant Reservations plugin for WordPress is vulnerable to a payment bypass via PHP type juggling in versions up to, and including, 2.7.16 This is due to the valid_payment() function using a PHP loose comparison (==) between the attacker-controlled payment_id POST parameter and the booking's stripe_payment_intent_id property. When an unauthenticated attacker submits a request to the nopriv AJAX handler rtb_stripe_pmt_succeed before the Stripe payment intent has been created for a booking (i.e., before the JavaScript-triggered create_stripe_pmtIntnt() call has stored an intent ID in post meta), the stripe_payment_intent_id property on the booking object remains null. The comparison sanitize_text_field('') == null evaluates to TRUE in PHP loose comparison, causing the payment verification check to pass with zero actual payment. This makes it possible for unauthenticated attackers to mark any existing payment_pending booking as paid without completing a Stripe payment by submitting an empty payment_id parameter.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Five Star Restaurant Reservations – WordPress Booking Plugin

All 15
More vulnerabilities in Five Star Restaurant Reservations – WordPress Booking Plugin
SeverityVulnerabilityCVEPublished
Medium5.3Unauthenticated Information Exposure
≤2.7.24Update to 2.8.0
CVE-2026-103334
Medium4.3Missing Authorization
<2.7.23Update to 2.7.23
CVE-2026-15151
Medium5.3Unauthenticated Insecure Direct Object Reference to Payment Bypass
≤2.7.22Update to 2.7.23
CVE-2026-15147
Medium5.3Missing Authorization
≤2.7.19Update to 2.7.20
CVE-2026-54830
Medium5.3Missing Authorization
≤2.7.14Update to 2.7.15
CVE-2026-42670

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?