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

CVE-2025-30891

HIGH · 8.8 CVSS v3.1 Published 2025-03-27
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in magepeopleteam WpTravelly tour-booking-manager allows PHP Local File Inclusion.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 · high confidence

This is a PHP Local File Inclusion (LFI) vulnerability in the WpTravelly WordPress plugin (by magepeopleteam). The flaw allows attackers to manipulate file path parameters in PHP include/require statements to traverse directories and include arbitrary PHP files from the local server, potentially leading to code execution.

MitigationUpdate WpTravelly plugin to the latest version when available; if no patch exists, disable the plugin or implement WAF rules to block directory traversal patterns (e.g., ../ sequences) in request 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
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
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'WpTravelly' or 'tour-booking-manager' in the list of active or inactive plugins
    Affected if The plugin appears in the WordPress plugin list, regardless of activation status
  2. Identify the installed WpTravelly version
    In the plugin list, click on WpTravelly to view its details, or check the plugin's main PHP file (typically in wp-content/plugins/wptravelly/ or similar) for a 'Version' header comment. Compare this version number to the affected version range provided in CVE-2025-30830891 advisories
    Affected if The installed version falls within the vulnerable version range or cannot be determined (unknown versions should be treated as potentially affected)
  3. Locate file inclusion functionality
    Examine the plugin directory for PHP files containing include, require, include_once, or require_once statements that use variables in the file path (e.g., include($_GET['file']). Search for common vulnerable parameter names such as 'file', 'template', 'page', 'path', or 'load' in the plugin's PHP files
    Affected if The plugin contains file inclusion functions that accept user-controlled input without proper sanitization
  4. Test for directory traversal accessibility
    If a vulnerable parameter is identified (e.g., ?file=../../), attempt to access a known local file via the plugin's URL endpoint. For example, request a path like ?file=../../../../wp-config.php (adjust traversal depth based on the plugin's installation path). Note: Only perform this test on systems you have explicit authorization to test
    Affected if The plugin allows directory traversal sequences (..) in the file parameter and successfully includes files outside the intended directory
  5. Check plugin configuration and access controls
    Review the plugin's PHP files to determine if the vulnerable file inclusion code is protected by authentication or access controls. Check if the functionality is reachable without admin privileges
    Affected if The vulnerable file inclusion endpoint is accessible to unauthenticated users or users without administrative privileges

If WpTravelly is installed and contains file inclusion code using unsanitized user input, the environment is vulnerable to CVE-2025-30891 regardless of whether the exact version matches a published range.

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 when available; if no patch exists, disable the plugin or implement WAF rules to block directory traversal patterns (e.g., ../ sequences) in request parameters.

Recommended fix Moderate confidence

Version 1.8.8 or later (check WordPress plugin repository for latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WpTravelly (WpTravelly tour-booking-manager) plugin
  4. 4. Check if an update is available. If an update to version 1.8.8 or later is available, update the plugin
  5. 5. If no update is available through the WordPress admin, download the latest version from the official WordPress plugin repository or the vendor's website
  6. 6. Deactivate and delete the current vulnerable version, then upload and install the updated version
  7. 7. Verify the plugin is running at version 1.8.8 or later
  8. 8. Test the tour booking functionality to ensure the update does not break existing features
Caveat Minor - verify tour booking and related functionality after update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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-30891 — 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-30891 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