dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-64373

HIGH · 8.1 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in shinetheme Traveler traveler allows PHP Local File Inclusion.This issue affects Traveler: from n/a through < 3.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 · high confidence

The Traveler WordPress theme contains a Local File Inclusion (LFI) vulnerability where unsanitized user input is used in PHP include/require statements, allowing attackers to read sensitive local files such as configuration files, wp-config.php, or other system files. This improper control of filename for include statements enables unauthorized file access.

MitigationUpdate Traveler theme to version 3.2.6 or later. If immediate patching is not feasible, implement web server-level access controls to block requests to vulnerable endpoints and add input validation/sanitization to filter directory traversal sequences (..) from all file inclusion parameters.

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

CVSS:3.1/AV:N/AC:H/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. Identify Traveler theme installation
    In WordPress admin dashboard, go to Appearance > Themes to confirm Traveler theme is active. Alternatively, check the theme directory at /wp-content/themes/traveler/ for the style.css file and read the Version header.
    Affected if Traveler theme is installed and active
  2. Determine Traveler theme version
    Open /wp-content/themes/traveler/style.css and locate the 'Version:' line in the file header comments. Note the exact version number.
    Affected if Version is present and less than 3.2.6
  3. Locate vulnerable include/require parameters
    Search theme PHP files for include, require, include_once, or require_once statements that use $_GET, $_POST, or $_REQUEST variables without sanitization. Focus on files in /inc or /includes directories.
    Affected if Unsanitized file inclusion parameters are found in the theme code
  4. Check for directory traversal exploitation attempts
    Review web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests containing ../ sequences or /wp-config.php in query parameters targeting theme files.
    Affected if Suspicious requests with traversal patterns are found in logs targeting the theme

If Traveler theme version is below 3.2.6 and the theme is active, the environment is vulnerable to LFI and should be investigated for signs of exploitation.

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 Traveler theme to version 3.2.6 or later. If immediate patching is not feasible, implement web server-level access controls to block requests to vulnerable endpoints and add input validation/sanitization to filter directory traversal sequences (..) from all file inclusion parameters.

Recommended fix High confidence

Traveler version 3.2.6

  1. 1. Back up your WordPress site database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Appearance > Themes.
  3. 3. Locate the Traveler theme and check for an available update to version 3.2.6.
  4. 4. If an update is available, update to Traveler version 3.2.6.
  5. 5. Alternatively, download Traveler version 3.2.6 from the official theme source and upload it via WordPress admin > Appearance > Themes > Add New > Upload Theme.
  6. 6. Verify the theme version is 3.2.6 after updating.
  7. 7. Test that the application functions normally after the upgrade.

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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