# CVE-2026-4911: Booking Package <= 1.7.06 - Unauthenticated Price Manipulation via 'amount' Parameter

> Unauthenticated attackers can manipulate booking prices by bypassing server-side validation, allowing them to purchase services at arbitrary low costs.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-2276-pc6c-j8wg

## What is CVE-2026-4911?

CVE-2026-4911 is a medium-severity vulnerability in masaakitanaka Booking Package, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Booking Package plugin for WordPress is vulnerable to Price Manipulation in versions up to, and including, 1.7.06 This is due to the intentForStripe() function passing user-controlled $_POST['amount'] directly to the Stripe PaymentIntent API without validation, and the commitStripe() function ignoring the server-calculated amount when confirming the payment. While the server correctly calculates the booking cost via getAmount() based on services, guests, taxes, and coupons, this calculated amount is never validated against or used to update the PaymentIntent because the critical code in CreditCard.php that would include the calculated amount in the PaymentIntent update is commented out. This makes it possible for unauthenticated attackers to book services at arbitrary prices (e.g., $0.01 instead of $500.00) by manipulating the amount parameter during PaymentIntent creation and completing the booking with the fraudulent payment.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

## Which versions are affected by CVE-2026-4911?


## How do I fix CVE-2026-4911?

No fix has been published for CVE-2026-4911 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4911 being exploited?

There is no known exploitation of CVE-2026-4911 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4911 and fix it if it is affected.

What it is: CVE-2026-4911 is a medium-severity vulnerability in masaakitanaka Booking Package, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4911 in the wild and no public exploit code.

Affected product: masaakitanaka Booking Package. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4911/ (Markdown: https://insights.sbomify.com/CVE-2026-4911/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4911
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4911
- OSV: https://osv.dev/vulnerability/CVE-2026-4911

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4911/
Summaries are generated and may contain mistakes; the official description above is the record.