Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-26921

HIGH · 8.8 CVSS v3.1 Published 2025-03-15
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 Booking and Rental Manager booking-and-rental-manager-for-woocommerce allows Object Injection.This issue affects Booking and Rental Manager: from n/a through <= 2.2.6.

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 · moderate confidence

A PHP Object Injection vulnerability exists in the magepeopleteam Booking and Rental Manager plugin for WooCommerce. The plugin deserializes untrusted data (likely via PHP's unsafe unserialize() function on user-supplied input), allowing an attacker to inject crafted PHP objects. This can potentially lead to remote code execution if the application has vulnerable classes with magic methods like __destruct() or __wakeup().

MitigationApply the latest plugin update from the vendor that replaces unsafe deserialization with safe alternatives (e.g., json_decode). If no patch is available, disable the plugin until a fix is released.

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. Confirm the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Booking and Rental Manager for WooCommerce' by MagePeople Team, or use WP-CLI: wp plugin list --name='booking-and-rental-manager-for-woocommerce'
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In WordPress admin > Plugins, click on the plugin to view version details, or check the plugin header in /wp-content/plugins/booking-and-rental-manager-for-woocommerce/ or similar path, or use WP-CLI: wp plugin get booking-and-rental-manager-for-woocommerce --field=version
    Affected if Version cannot be determined or is earlier than the patched version
  3. Verify WooCommerce is active
    In WordPress admin > Plugins, confirm WooCommerce is active, or check wp_options table for option_name='active_plugins' containing WooCommerce
    Affected if WooCommerce is active and the vulnerable plugin is present (the plugin only operates within WooCommerce context)
  4. Identify deserialization entry points
    Search plugin files for unserialize() calls without prior sanitization, typically in AJAX handlers or form processing files. Common locations: /includes/class-ajax.php, /public/class-shortcode.php, or any file handling submitted booking/order data
    Affected if The plugin contains unserialize() calls on user-supplied input without validation (this is the vulnerable condition)

You are affected if the magepeopleteam Booking and Rental Manager plugin is installed, WooCommerce is active, and the plugin code contains unprotected unserialize() calls processing user input.

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

Apply the latest plugin update from the vendor that replaces unsafe deserialization with safe alternatives (e.g., json_decode). If no patch is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Version 2.2.7 or later (the first version after 2.2.6)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Booking and Rental Manager for WooCommerce' by MagePeople Team
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update appears in WordPress, manually download the latest version from the WordPress plugin repository or contact the vendor
  6. 6. After updating, verify the plugin is functioning correctly on the booking/rental pages
  7. 7. Clear any caching plugins or server-side caches to ensure changes take effect

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-26921 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