CVE-2025-49308: WP Travel Engine · PHP Remote File Inclusion
Affects WP Travel EngineSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Travel Engine WP Travel Engine | Affected
| Fixed in– |
AI-suggested
- Immediate audit of all WP Travel Engine plugin instances to identify affected versions (up to 6.5.1).
- Restrict file inclusion paths by implementing strict input validation and sanitization on any parameters controlling file paths in the plugin code.
- Employ web application firewalls (WAFs) with rules designed to detect and block suspicious include/require parameter manipulations.
- Limit PHP process permissions to prevent reading or executing unauthorized files, applying the principle of least privilege on the web server.
- Monitor logs for unusual file access patterns or errors related to include/require statements.
- Until an official patch is released, consider disabling or replacing the WP Travel Engine plugin if feasible.
- Harden the WordPress environment by disabling PHP functions like allow_url_include and restricting file system access.
- Educate development and security teams about the risks of improper file inclusion and enforce secure coding practices for plugin development and customization.
- Prepare incident response plans specific to LFI attacks to quickly contain and remediate any exploitation attempts.
Description
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in WP Travel Engine WP Travel Engine allows PHP Local File Inclusion. This issue affects WP Travel Engine: from n/a through 6.5.1.