# CVE-2026-15229: Pinpoint Booking System <= 2.9.9.7.1 - Unauthenticated Arbitrary Booking Price Manipulation

> Unauthenticated attackers can manipulate booking prices to zero and obtain instantly-approved reservations by bypassing server-side validation.

- **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:** 10 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-2jwj-8g7h-f5p5

## What is CVE-2026-15229?

CVE-2026-15229 is a medium-severity vulnerability in Unknown Pinpoint Booking System, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Pinpoint Booking System  WordPress plugin through 2.9.9.7.1 does not validate the booking price on the server side, allowing unauthenticated users to create bookings at an arbitrary price (including zero) and, by selecting a specific payment method, obtain an instantly-approved reservation.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-15229 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15229 is a medium-severity vulnerability in Unknown Pinpoint Booking System, published on 10 Aug 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-15229 in the wild and no public exploit code.

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

## Sources

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

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