dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-30892

HIGH · 8.8 CVSS v3.1 Published 2025-04-01
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 WpTravelly tour-booking-manager allows Object Injection.This issue affects WpTravelly: from n/a through <= 1.8.7.

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

PHP Object Injection vulnerability in the WpTravelly WordPress plugin's tour booking manager allows attackers to deserialize untrusted data, potentially leading to remote code execution if malicious PHP objects are crafted and magic methods exist in the application or installed plugins.

MitigationUpdate WpTravelly plugin to the latest version beyond 1.8.7, or if no patch is available, remove 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. Verify WpTravelly plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WpTravelly' or check the /wp-content/plugins/ directory for the wptravelly folder
    Affected if The WpTravelly plugin is present in the WordPress installation
  2. Check installed WpTravelly version
    In WordPress admin, go to Plugins > Installed Plugins > WpTravelly and view the version number, or read the main plugin file header at /wp-content/plugins/wptravelly/wptravelly.php for the 'Version' tag
    Affected if The version is 1.8.7 or earlier (the vulnerability is fixed in versions beyond 1.8.7)
  3. Confirm tour booking manager is accessible
    Navigate to the WP Travelly tour booking functionality in the admin panel or check if the /tour-booking-manager/ endpoint is publicly accessible on the site
    Affected if The tour booking manager feature is enabled and accessible on the site
  4. Inspect the vulnerable deserialization point
    Examine the wptravelly plugin files, specifically looking for unserialize() calls in the tour booking manager component (typically in admin/class-wptravelly-admin.php or similar class files handling booking submissions)
    Affected if Code contains unserialize() handling user-supplied data without validation

A site is affected if WpTravelly plugin version 1.8.7 or earlier is installed with the tour booking manager feature enabled, and the vulnerable deserialization code is present.

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 WpTravelly plugin to the latest version beyond 1.8.7, or if no patch is available, remove the plugin until a fix is released.

Recommended fix Moderate confidence

Latest available version of WpTravelly (check WordPress plugin repository for current version > 1.8.7)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the WpTravelly plugin (by magepeopleteam)
  4. 4. Check the current version is 1.8.7 or below
  5. 5. Update the plugin to the latest available version from the WordPress plugin repository
  6. 6. Verify the update completes successfully
  7. 7. Test the tour-booking functionality to ensure the site functions correctly after the update

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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