dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-67997

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-20
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
Deserialization of Untrusted Data vulnerability in BoldThemes Travelicious travelicious allows Object Injection.This issue affects Travelicious: from n/a through < 1.6.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

This is a PHP Object Injection vulnerability in the BoldThemes Travelicious WordPress theme. The vulnerability allows remote attackers to deserialize untrusted data, potentially leading to remote code execution if exploitable PHP classes (gadget chains) are available in the application environment.

MitigationUpdate Travelicious theme to version 1.6.7 or later. If immediate patching is not possible, disable the theme until the update can be applied. Review application for any available PHP gadget classes that could be chained for RCE.

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 Travelicious theme installation
    In the WordPress admin dashboard, go to Appearance > Themes and verify if the Travelicious theme by BoldThemes is installed and active.
    Affected if The Travelicious theme is installed and activated.
  2. Identify installed theme version
    Access the theme's style.css file (typically at /wp-content/themes/travelicious/style.css) and locate the 'Version:' header in the file comments, or check the theme version displayed in the WordPress themes admin panel.
    Affected if The installed version is lower than 1.6.7.
  3. Check for vulnerable deserialization usage
    Search the theme's PHP files for calls to unserialize() on untrusted input (such as $_GET, $_POST, or $_COOKIE parameters). Common patterns include: unserialize($_POST['data']), unserialize($_GET['param']), or similar. Use grep or a file search in the /wp-content/themes/travelicious directory.
    Affected if The theme code contains unserialize() calls processing user-supplied input without prior validation.
  4. Review plugin and theme environment for gadget classes
    Enumerate installed plugins and additional themes that may contain PHP classes suitable for gadget chain exploitation. In a PHP Object Injection attack, these classes are used to chain malicious object creation. Check for classes with magic methods (__wakeup, __destruct, __toString) in the /wp-content/plugins and /wp-content/themes directories.
    Affected if Any installed plugins or themes contain classes with exploitable magic methods that could form a gadget chain.
  5. Inspect application logs for injection attempts
    Review web server access logs and WordPress debug logs (wp-content/debug.log if enabled) for patterns indicating deserialization payload delivery, such as base64-encoded serialized PHP objects in request parameters.
    Affected if Logs show suspicious serialized data patterns in incoming requests.

A user is affected if they have the Travelicious theme active at a version below 1.6.7 AND the theme processes untrusted serialized data, with or without gadget chains present in the environment.

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 Travelicious theme to version 1.6.7 or later. If immediate patching is not possible, disable the theme until the update can be applied. Review application for any available PHP gadget classes that could be chained for RCE.

Recommended fix Moderate confidence

Travelicious theme version 1.6.7

  1. Upgrade the Travelicious theme to version 1.6.7 or later to resolve the deserialization vulnerability
  2. Verify the upgrade in a staging environment before deploying to production
  3. After upgrading, review any newly released theme documentation for additional security configurations

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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