Authenticated code execution via local file inclusion
Published Jun 6, 2025 · Updated Apr 28, 2026
Local file inclusion in WP Travel Engine 6.5.1 and earlier allows remote authenticated users to execute server-side PHP files. Public records establish that an attacker-controlled filename reaches a PHP include or require operation, but they do not identify the vulnerable function or request parameter. Contributor-level access is required; included files can disclose server data or execute PHP code already present on the server.
Summary
What happened
Local file inclusion in WP Travel Engine 6.5.1 and earlier allows remote authenticated users to execute server-side PHP files. Public records establish that an attacker-controlled filename reaches a PHP include or require operation, but they do not identify the vulnerable function or request parameter. Contributor-level access is required; included files can disclose server data or execute PHP code already present on the server.
The record
- CVE
- CVE-2025-49308
- Published
- Jun 6, 2025
- Updated
- Apr 28, 2026
- Vendor
- Digital Thrive Labs Inc.
- Product
- WP Travel Engine
- Classifications
- CWE-98, CAPEC-252, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 6, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=6.5.1 changes=[{"at":"6.5.2","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo