# CVE-2026-59532: WordPress Booking and Rental Manager plugin <= 2.7.2 - Price Manipulation vulnerability

> Unauthenticated attackers can manipulate prices in the Booking and Rental Manager plugin, leading to unauthorized financial transactions.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-qw7x-5wxq-5xxq

## What is CVE-2026-59532?

CVE-2026-59532 is a high-severity vulnerability in magepeopleteam Booking and Rental Manager, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated Other Vulnerability Type in Booking and Rental Manager <= 2.7.2 versions.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

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


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

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

## Is CVE-2026-59532 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59532 is a high-severity vulnerability in magepeopleteam Booking and Rental Manager, published on 27 Jul 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-59532 in the wild and no public exploit code.

Affected product: magepeopleteam Booking and Rental Manager. 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-59532/ (Markdown: https://insights.sbomify.com/CVE-2026-59532/index.md)
```

## Sources

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

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