# CVE-2026-15149: WP Hotel Booking < 2.3.3 - Unauthenticated Payment Bypass via Price Manipulation

> Unauthenticated attackers can manipulate booking prices to create free or discounted reservations in the WP Hotel Booking plugin.

- **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:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-9rjp-x5g7-g983

## What is CVE-2026-15149?

CVE-2026-15149 is a medium-severity vulnerability in Unknown WP Hotel Booking, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Hotel Booking WordPress plugin before 2.3.3 does not ensure that room quantities and the resulting order total are non-negative when placing a booking, and relies on client-controlled cart data, allowing unauthenticated users to create confirmed reservations for free or at an arbitrarily reduced price.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-15149 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15149 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15149 is a medium-severity vulnerability in Unknown WP Hotel Booking, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15149 exists.

Affected product: Unknown WP Hotel Booking. 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-15149/ (Markdown: https://insights.sbomify.com/CVE-2026-15149/index.md)
```

## Sources

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

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