Skip to main content
VulnerabilityPublished

CVE-2026-131732: Taxi Booking Manager for WooCommerce (WordPress plugin) · Missing Authorization

Affects Taxi Booking Manager for WooCommerce (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.2.11 when convenient.

Data as of 20 Nov 2026, 11:35 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Patchstack)CVSS 3.14.3
Patch
Available – fixed in 2.2.11
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade Taxi Booking Manager for WooCommerce (WordPress plugin) to 2.2.11.

Affected software

ProductAffectedFixed in
Taxi Booking Manager for WooCommerceecab-taxi-booking-managerAffected
  • <2.2.11
Fixed in
  • 2.2.11

AI-suggested

Upgrade the Taxi Booking Manager for WooCommerce plugin to version 2.2.11 or later, where this missing authorization vulnerability has been fixed. No other mitigation is required as the patch fully addresses the issue.

Description

CVE-2026-131732 is a missing authorization vulnerability in Magepeople inc.'s Taxi Booking Manager for WooCommerce plugin. Versions from initial release up to 2.2.10 are affected. The flaw allows exploitation due to incorrectly configured access control security levels, potentially leading to unauthorized actions. The issue is fixed in version 2.2.11.

References

Community reviews

Loading reviews…