dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-4413

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The Hotel Booking Lite plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 4.11.1 via deserialization of untrusted input. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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

The Hotel Booking Lite WordPress plugin up to version 4.11.1 is vulnerable to PHP Object Injection through unsafe deserialization of untrusted input. Unauthenticated attackers can inject arbitrary PHP objects, and if a POP chain exists elsewhere on the target system (via another plugin or theme), this could enable arbitrary file deletion, data exfiltration, or code execution.

MitigationUpdate Hotel Booking Lite to the latest version immediately. Additionally, audit the WordPress installation for other plugins or themes that may provide exploitable POP chains.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Hotel Booking Lite plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the file wp-content/plugins/hotel-booking-lite/plugin.php and check the Version header in the plugin comments
    Affected if The plugin is present in the plugins directory with an active or inactive status
  2. Identify installed plugin version
    Read the Version field from the plugin header in wp-content/plugins/hotel-booking-lite/plugin.php or view it in the WordPress plugins admin page
    Affected if The version number is 4.11.1 or lower
  3. Locate the vulnerable deserialization function
    Search the plugin source code (especially in ajax handlers or public-facing files) for calls to unserialize() that process user-supplied input without validation, such as from $_POST, $_GET, or $_REQUEST parameters
    Affected if The plugin code contains unserialize() calls handling untrusted input and this functionality is accessible to unauthenticated users
  4. Check plugin exposure
    Determine if the vulnerable endpoint/function is publicly accessible without authentication by examining the plugin's capability checks or access modifiers on the identified unserialize() call
    Affected if The vulnerable deserialization is reachable by unauthenticated (not-logged-in) visitors
  5. Audit for POP chain gadgets
    Review other installed plugins and themes for classes with magic methods (__destruct, __wakeup, __toString, etc.) that could form a property-oriented programming chain when combined with the injected object
    Affected if Other plugins or themes contain exploitable POP chain gadgets that could be triggered by the injected PHP object

You are affected if Hotel Booking Lite version 4.11.1 or lower is installed, the plugin exposes an unauthenticated unserialize() on user input, AND a POP chain gadget exists elsewhere on the WordPress installation.

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 Hotel Booking Lite to the latest version immediately. Additionally, audit the WordPress installation for other plugins or themes that may provide exploitable POP chains.

Recommended fix Moderate confidence

Hotel Booking Lite version 4.12.0 or later

  1. Update the Hotel Booking Lite plugin to version 4.12.0 or later via the WordPress admin dashboard under Plugins > Installed Plugins, or use wp-cli plugin update hotel-booking-lite
  2. After updating, verify the plugin version reflects 4.12.0 or higher in the plugins list
  3. Ensure no other vulnerable plugins with potential POP chains are installed that could be chained with this vulnerability

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4413 — 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-2024-4413 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