WP Travel Engine: A security weakness
WP Travel Engine is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 6.8.1.
- Component
- WP Travel Engine
- Plugin slug
wp-travel-engine- Affected
- < 6.8.1
- Safe version
6.8.1- Published
- Jul 07, 2026
- Weakness
- Not assigned
This CVE was published Jul 07, 2026 and is one of 15 known issues for this plugin.
Update, patch or deactivate.
Update WP Travel Engine to 6.8.1 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L