CVE-2025-49308
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in WP Travel Engine WP Travel Engine wp-travel-engine allows PHP Local File Inclusion.This issue affects WP Travel Engine: from n/a through <= 6.5.1.
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 confidenceThe WP Travel Engine plugin for WordPress contains a Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in PHP include/require statements without proper sanitization. An attacker can manipulate file path parameters to read sensitive server files, potentially exposing configuration files like wp-config.php and leading to remote code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WP Travel Engine plugin is installedLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'WP Travel Engine' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-travel-engine' or similar.Affected if The plugin appears in the installed plugins list
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find WP Travel Engine, and note the version number displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/wp-travel-engine/ for the 'Version' comment.Affected if Version is within the vulnerable range (check against official WP Travel Engine security advisories for exact affected versions)
-
Identify vulnerable file path parametersReview plugin source code for include/require statements that use user-supplied input (like $_GET, $_POST, or $_REQUEST parameters) without proper sanitization. Look for patterns such as: include($_GET['file']); or require_once($some_variable); in the plugin's PHP files.Affected if Plugin code contains include/require statements using unsanitized user input for file paths
-
Test parameter accessibility without exploitationReview HTTP requests to the plugin's AJAX endpoints or front-end files that accept file path parameters. Use browser DevTools or a proxy to identify which parameters accept file paths and whether they are accessible to unauthenticated users.Affected if File path parameters are accessible and accept user-supplied values without validation
You are affected if WP Travel Engine plugin is installed with a vulnerable version AND the plugin exposes file path parameters that use unsanitized user input in PHP include/require statements.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate WP Travel Engine to the latest patched version. Until patched, disable PHP's allow_url_include setting, implement strict input validation on all file path parameters, and consider deploying a WAF rule to block directory traversal patterns.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49308 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49308 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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