dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-24661

HIGH · 8.8 CVSS v3.1 Published 2025-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of Untrusted Data vulnerability in magepeopleteam Taxi Booking Manager for WooCommerce ecab-taxi-booking-manager allows Object Injection.This issue affects Taxi Booking Manager for WooCommerce: from n/a through <= 1.1.8.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a PHP Object Injection vulnerability in the Taxi Booking Manager for WooCommerce plugin. The plugin deserializes untrusted data without proper validation, allowing attackers to inject malicious PHP objects that could lead to remote code execution, file inclusion, or database manipulation.

MitigationUpdate Taxi Booking Manager for WooCommerce to version 1.1.9 or later. If no update is available, disable the plugin immediately and seek an alternative solution. Review server logs for signs of exploitation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Taxi Booking Manager plugin is installed
    Navigate to WordPress admin > Plugins and check if 'Taxi Booking Manager for WooCommerce' appears in the installed plugins list, or inspect the /wp-content/plugins/ directory for a folder containing 'taxi-booking-manager'
    Affected if The plugin is not listed in your WordPress installation
  2. Determine the installed plugin version
    Access the plugin files via FTP or file manager, then open the main plugin PHP file (usually taxi-booking-manager.php) and locate the 'Version' header in the plugin comment block, or check the version stored in the WordPress database via phpMyAdmin in the wp_options table under the option_name containing 'taxi_booking_manager_version'
    Affected if You cannot locate a version number or the version is older than the patched release
  3. Compare your version to the affected range
    Since no specific CVE version range was provided, check the plugin's official WordPress repository page or vendor advisories for the version that addresses CVE-2025-24661; compare your identified version against any published vulnerable and patched version numbers
    Affected if Your installed version falls within a published vulnerable range or is older than the patched version
  4. Confirm the plugin is active on your site
    In WordPress admin > Plugins, verify the plugin status shows as 'Active', or query the wp_options table for option_name 'active_plugins' and check if it contains the plugin's base file reference
    Affected if The plugin is active and running on the site
  5. Inspect for deserialization usage in plugin code
    If you have file access, search the plugin directory for occurrences of unserialize() function calls - use grep or a text search tool to find patterns like 'unserialize($_' or 'unserialize($' within PHP files in the plugin folder
    Affected if The plugin code contains unserialize() calls processing untrusted input without validation
  6. Audit for potential PHP object injection gadget chains
    Review all installed plugins (not just Taxi Booking Manager) for classes with magic methods (__wakeup, __destruct, __toString) that could form a gadget chain; this requires code analysis or use of security scanning tools capable of detecting POP chains in the wp-content/plugins directory
    Affected if A gadget chain exists in your environment that could be exploited via the deserialization flaw

You are affected if Taxi Booking Manager for WooCommerce is installed, active, and running a version that falls within the vulnerable range published for CVE-2025-24661, combined with the presence of unserialize() handling untrusted data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Taxi Booking Manager for WooCommerce to version 1.1.9 or later. If no update is available, disable the plugin immediately and seek an alternative solution. Review server logs for signs of exploitation attempts.

Recommended fix Moderate confidence

1.1.9 (or latest available version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Taxi Booking Manager for WooCommerce' (magepeopleteam)
  4. 4. Check the current version number to confirm it is <= 1.1.8
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update was successful and test the booking functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24661 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24661 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data