CVE-2026-129027: Taxi Booking Manager for WooCommerce (WordPress plugin) · Missing Authorization
Affects Taxi Booking Manager for WooCommerce (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.2.10 when convenient.
Data as of 17 Nov 2026, 23:34 UTC
Thin evidence
One scorer or none| CNA (Patchstack) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 2.2.10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Taxi Booking Manager for WooCommerce (WordPress plugin) to 2.2.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Taxi Booking Manager for WooCommerceecab-taxi-booking-manager | Affected
| Fixed in
|
AI-suggested
Upgrade the Taxi Booking Manager for WooCommerce plugin to version 2.2.10 or later, where this missing authorization vulnerability has been fixed. No other mitigation is necessary as the issue is resolved in the official patch.
Description
CVE-2026-129027 is a missing authorization vulnerability in Magepeople inc.'s Taxi Booking Manager for WooCommerce plugin. Versions from initial release through 2.2.9 are affected. The flaw allows unauthorized users to exploit incorrectly configured access control, potentially leading to unauthorized modification of data. The issue has been fixed in version 2.2.10. The vulnerability has a CVSS 3.1 base score of 5.3, indicating medium severity, with no confidentiality or availability impact but integrity impact possible without user interaction.