CVE-2026-4911: CWE-472 External Control of Assumed-Immutable Web Parameter in masaakitanaka Booking Package
The Booking Package plugin for WordPress up to version 1.7.06 contains a vulnerability allowing unauthenticated attackers to manipulate booking prices by altering the amount parameter sent to the Stripe PaymentIntent API. The plugin fails to validate or enforce the server-calculated booking cost during payment confirmation, enabling attackers to pay arbitrary amounts, potentially much lower than the actual service cost. This issue arises because the critical code that would update the PaymentIntent with the correct amount is commented out. The vulnerability is classified under CWE-472 (External Control of Assumed-Immutable Web Parameter) and has a CVSS score of 5.3, indicating medium severity. No official patch or remediation guidance is currently available from the vendor.
AI Analysis
Technical Summary
CVE-2026-4911 affects the Booking Package WordPress plugin by allowing price manipulation through external control of the 'amount' parameter in the Stripe PaymentIntent API calls. The intentForStripe() function passes the user-controlled $_POST['amount'] directly without validation, and the commitStripe() function does not verify the server-calculated amount when confirming payments. Although the server calculates the correct booking cost via getAmount(), this value is not enforced because the code responsible for updating the PaymentIntent with the correct amount is commented out in CreditCard.php. This flaw permits unauthenticated attackers to complete bookings at arbitrary prices, bypassing intended payment amounts.
Potential Impact
The vulnerability allows attackers to pay less than the legitimate booking cost by manipulating the payment amount parameter, leading to financial loss for the service provider. There is no impact on confidentiality or availability reported. The integrity of payment transactions is compromised due to the acceptance of fraudulent payment amounts.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider disabling the affected plugin or implementing custom validation to enforce server-calculated amounts before initiating Stripe PaymentIntents. Monitoring for suspicious booking activity may help detect exploitation attempts.
CVE-2026-4911: CWE-472 External Control of Assumed-Immutable Web Parameter in masaakitanaka Booking Package
Description
The Booking Package plugin for WordPress up to version 1.7.06 contains a vulnerability allowing unauthenticated attackers to manipulate booking prices by altering the amount parameter sent to the Stripe PaymentIntent API. The plugin fails to validate or enforce the server-calculated booking cost during payment confirmation, enabling attackers to pay arbitrary amounts, potentially much lower than the actual service cost. This issue arises because the critical code that would update the PaymentIntent with the correct amount is commented out. The vulnerability is classified under CWE-472 (External Control of Assumed-Immutable Web Parameter) and has a CVSS score of 5.3, indicating medium severity. No official patch or remediation guidance is currently available from the vendor.
CVSS v3.1
Score 5.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-4911 affects the Booking Package WordPress plugin by allowing price manipulation through external control of the 'amount' parameter in the Stripe PaymentIntent API calls. The intentForStripe() function passes the user-controlled $_POST['amount'] directly without validation, and the commitStripe() function does not verify the server-calculated amount when confirming payments. Although the server calculates the correct booking cost via getAmount(), this value is not enforced because the code responsible for updating the PaymentIntent with the correct amount is commented out in CreditCard.php. This flaw permits unauthenticated attackers to complete bookings at arbitrary prices, bypassing intended payment amounts.
Potential Impact
The vulnerability allows attackers to pay less than the legitimate booking cost by manipulating the payment amount parameter, leading to financial loss for the service provider. There is no impact on confidentiality or availability reported. The integrity of payment transactions is compromised due to the acceptance of fraudulent payment amounts.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider disabling the affected plugin or implementing custom validation to enforce server-calculated amounts before initiating Stripe PaymentIntents. Monitoring for suspicious booking activity may help detect exploitation attempts.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-26T16:12:47.440Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69f0602fcbff5d8610cfd2d4
Added to database: 4/28/2026, 7:22:23 AM
Last enriched: 5/6/2026, 2:15:38 AM
Last updated: 6/12/2026, 12:20:37 PM
Views: 91
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.