dbcve.org
Backpack TravelerWordPress extension · Qodeinteractive

CVE-2025-39490

HIGH · 8.1 CVSS v3.1 Published 2025-05-23
Fix available
A fix is available. Upgrade to 2.10.3 or later.
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 Mikado-Themes Backpack Traveler backpacktraveler allows PHP Local File Inclusion.This issue affects Backpack Traveler: from n/a through <= 2.10.2.

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

The Backpack Traveler WordPress theme (versions up to 2.10.2) contains a PHP Local File Inclusion (LFI) vulnerability where the application improperly controls filenames used in include/require statements. Attackers can manipulate input parameters to include arbitrary local files from the server, potentially exposing sensitive configuration files, credentials, or other system files.

MitigationSanitize and validate all user-supplied input used in PHP include/require statements. Use whitelist-based validation for allowed files/directories, avoid direct use of user input in file paths, and implement proper access controls to prevent traversal outside intended directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Backpack TravelerWordPress extension
Affected:< 2.10.3

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 installed theme version
    Access the WordPress admin dashboard, navigate to Appearance > Themes, and locate the Backpack Traveler theme to view its version number. Alternatively, inspect the style.css file in the theme directory or check the version declared in the theme's functions.php file.
    Affected if The displayed version is below 2.10.3 (for example, 2.10.2, 2.10.1, or any version listed as 2.10.2 and lower).
  2. Locate theme directory path
    Access your WordPress installation via FTP or file manager and navigate to wp-content/themes/ and identify the backpack-traveler theme folder. Note the absolute path to this directory.
    Affected if The theme folder exists and contains the vulnerable theme files.
  3. Identify vulnerable include/require patterns
    Search the theme's PHP files (particularly in main template files, header.php, footer.php, or any file handling template includes) for code that uses variables or request parameters in include, require, include_once, or require_once statements without proper sanitization. Use grep or a code editor to search for patterns like 'include($', 'require($', or 'include_once($_'.
    Affected if Any PHP file in the theme uses unsanitized user input (such as $_GET, $_POST, or $_REQUEST variables) directly in include/require statements.
  4. Check for exposed vulnerable parameters
    Review the theme's PHP files for parameters that might be controllable via URL query strings (for example, parameters named 'template', 'file', 'page', or 'path'). Test by attempting to access common WordPress page URLs with added query parameters referencing local files (for example, ?template=../../../../wp-config.php).
    Affected if The application returns the contents of files you request, indicating the LFI vulnerability is present and exploitable.

You are affected if your installed Backpack Traveler theme version is below 2.10.3 AND your server returns file contents when requesting local file paths through theme parameters.

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
Upgrade available Upgrade to 2.10.3 or later
Fixed in 2.10.3
Interim mitigation

Sanitize and validate all user-supplied input used in PHP include/require statements. Use whitelist-based validation for allowed files/directories, avoid direct use of user input in file paths, and implement proper access controls to prevent traversal outside intended directories.

Recommended fix High confidence

Backpack Traveler 2.10.3

  1. Back up the entire website including database and files before performing any updates
  2. Download Backpack Traveler version 2.10.3 or latest version from the official Mikado-Themes source
  3. Update the theme through the WordPress admin dashboard or via FTP upload of the new version
  4. Verify the update was applied successfully by checking the theme version in WordPress admin
  5. Confirm the PHP Local File Inclusion vulnerability is no longer exploitable

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

Fix this in Backpack Traveler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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