CVE-2026-6498 json
Five Star Restaurant Reservations <= 2.7.16 - Unauthenticated Payment Bypass via PHP Type Juggling in 'payment_id' Parameter
published 2026-04-30 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-26361
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- rustaurius Five Star Restaurant Reservations – WordPress Booking Plugin
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/8ee08aac-7bcc-4809-a5aa-7b95ed736f19?source=cve
- plugins.trac.wordpress.org /browser/restaurant-reservations/trunk/includes/PaymentGatewayStripe.class.php#L458
- plugins.trac.wordpress.org /browser/restaurant-reservations/tags/2.7.13/includes/PaymentGatewayStripe.class.php#L458
- plugins.trac.wordpress.org /browser/restaurant-reservations/trunk/includes/PaymentGatewayStripe.class.php#L404
- plugins.trac.wordpress.org /browser/restaurant-reservations/tags/2.7.13/includes/PaymentGatewayStripe.class.php#L404
- plugins.trac.wordpress.org /changeset/3518833/restaurant-reservations/trunk/includes/PaymentGatewayStripe.class.php
- plugins.trac.wordpress.org /changeset?old_path=%2Frestaurant-reservations/tags/2.7.16&new_path=%2Frestaurant-reservations/tags/2.7.17
Sources
- CVE List CVE-2026-6498
- NVD CVE-2026-6498
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.