WP Travel Engine – Tour Booking Plugin – Tour Operator Software <= 6.6.7 - Authenticated (Subscriber+) Arbitrary File Deletion via File Renaming
Strategic Overview
- Status
- Patched in 6.6.8
- Affected Version
<= 6.6.7- CVSS
- 9.8Critical
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-7526
At a glance
CVE-2025-7526 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP Travel Engine WordPress plugin, affecting versions <= 6.6.7. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.6.8; sites on affected versions should update now. Disclosed October 2025, reported by wesley (wcraft).
Vulnerability Overview
The WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress is vulnerable to arbitrary file deletion (via renaming) due to insufficient file path validation in the set_user_profile_image function in all versions up to, and including, 6.6.7. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in WP Travel Engine <= 6.6.7 takes an account at Subscriber level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For WP Travel Engine the fix is 6.6.8: builds <= 6.6.7 are affected, anything from 6.6.8 onward is not.
Remediation
Update to version 6.6.8, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Travel Engine 6.6.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP Travel Engine – Tour Booking Plugin – Tour Operator Software
- 10.0CVE-2024-30502: WP Travel Engine <= 5.7.9 SQL Injection
CVE-2024-30502 - 9.8CVE-2025-7634: WP Travel Engine LFI
CVE-2025-7634 - 9.8CVE-2025-30870: WP Travel Engine <= 6.3.5 Local File Inclusion
CVE-2025-30870 - 9.1CVE-2024-30504: WP Travel Engine <= 5.7.9 SQL Injection
CVE-2024-30504 - 8.8CVE-2025-49308: WP Travel Engine <= 6.5.1 Local File Inclusion
CVE-2025-49308 - 8.8CVE-2025-30871: WP Travel Engine <= 6.3.5 Local File Inclusion
CVE-2025-30871 - 8.1CVE-2026-49770: WP Travel Engine PHP Object Injection
CVE-2026-49770 - 7.5CVE-2026-17087: WP Travel Engine Unauthenticated Info Disclosure
CVE-2026-17087
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C