# CVE-2026-84045: E-cab Taxi Booking Manager for Woocommerce < 2.0.5 - Unauthenticated Price Manipulation via mptbm_add_to_cart

> Unauthenticated attackers can manipulate taxi booking prices to zero by bypassing server-side validation of trip distance and base price.

- **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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-5h32-fhrg-6q48

## What is CVE-2026-84045?

CVE-2026-84045 is a medium-severity vulnerability in Unknown E-cab Taxi Booking Manager for Woocommerce, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The E-cab Taxi Booking Manager for Woocommerce WordPress plugin before 2.0.5 does not validate a client-supplied trip distance and base-price value on the server before pricing a booking, allowing unauthenticated attackers to manipulate the order total down to zero and place real taxi-booking orders at an arbitrary price.

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


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

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

## Is CVE-2026-84045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84045 is a medium-severity vulnerability in Unknown E-cab Taxi Booking Manager for Woocommerce, published on 4 Sep 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-84045 in the wild and no public exploit code.

Affected product: Unknown E-cab Taxi Booking Manager for Woocommerce. 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-84045/ (Markdown: https://insights.sbomify.com/CVE-2026-84045/index.md)
```

## Sources

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

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