# CVE-2026-103351: WordPress Taxi Booking Manager for WooCommerce plugin <= 2.1.1 - Other vulnerability Type vulnerability

> Attackers can manipulate input data due to improper quantity validation in the Taxi Booking Manager for WooCommerce 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:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-hh49-m68v-pcf8

## What is CVE-2026-103351?

CVE-2026-103351 is a medium-severity vulnerability in Magepeople inc. Taxi Booking Manager for WooCommerce, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Validation of Specified Quantity in Input vulnerability in Magepeople inc. Taxi Booking Manager for WooCommerce ecab-taxi-booking-manager allows Input Data Manipulation.This issue affects Taxi Booking Manager for WooCommerce: from n/a through 2.1.1.

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

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


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

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

## Is CVE-2026-103351 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103351 is a medium-severity vulnerability in Magepeople inc. Taxi Booking Manager for WooCommerce, published on 5 Oct 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-103351 in the wild and no public exploit code.

Affected product: Magepeople inc. 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-103351/ (Markdown: https://insights.sbomify.com/CVE-2026-103351/index.md)
```

## Sources

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

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