CVE-2026-6498
Last modified
CVE-2026-6498 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-6498?
How severe is CVE-2026-6498?
How do I fix CVE-2026-6498?
How Strix Helps
- Same Subject, Wrong User: A Cross-Issuer Account Takeover in n8nStrix found an identity-binding bug in n8n's token-exchange flow enabling account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64968ATutor is vulnerable to Server-Side request forgery in impor…5.1
- CVE-2026-64969ATutor is vulnerable to Insecure Direct Object Reference (ID…5.3
- CVE-2026-6497A vulnerability was determined in prasathmani TinyFileManage…6.3
- CVE-2026-64970ATutor is vulnerable to Stored Cross Site Scripting in regis…5.1
- CVE-2026-64971ATutor is vulnerable to Reflected XSS in restore functionali…4.8
- CVE-2026-64972ATutor is vulnerable to Reflected XSS via popup parameter in…4.8
- CVE-2026-6499Incorrect Permission Assignment for Critical Resource vulner…2.4
- CVE-2026-64993Dell RVTools versions prior to 4.8.1, contains an improper c…9.1
- CVE-2026-6500Plaintext storage of a password vulnerability in ILM Informa…4.8
- CVE-2026-65007The Grav api plugin (grav-plugin-api) before 1.0.8 fails to …9.6
- CVE-2026-65008Grav 2.0.4 (fixed in 2.0.7) contains a remote code execution…9.8
- CVE-2026-65009OpenRemote versions before 1.26.2 contain an information dis…5.3
Are you affected by CVE-2026-6498?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
