CVE-2026-10834: WP Travel Engine · External Control of File Name or Path
Affects WP Travel EngineSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium : upgrade to 6.8.1 when convenient.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 7 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 19 Nov 2026.
What to do
Upgrade WP Travel Engine to 6.8.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Travel Engine | Affected
| Fixed in
|
AI-suggested
Since the vulnerability affects versions before 6.8.1, upgrading to version 6.8.1 or later (if available) is recommended once confirmed. If you cannot patch yet, restrict user permissions where possible and monitor for unusual file movements within the uploads directory.
Description
The WP Travel Engine WordPress plugin before 6.8.1 does not properly validate the source of a user-supplied profile image path before moving the file, allowing authenticated users with subscriber-level access and above to relocate arbitrary files within the WordPress uploads directory into their own profile-image path. This removes the targeted media from its original location and can break content across the site.