Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-7526: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in wptravelengine WP Travel Engine – Tour Booking Plugin – Tour Operator Software

0
Critical
VulnerabilityCVE-2025-7526cvecve-2025-7526cwe-22
Published: Thu Oct 09 2025 (10/09/2025, 05:23:52 UTC)
Source: CVE Database V5
Vendor/Project: wptravelengine
Product: WP Travel Engine – Tour Booking Plugin – Tour Operator Software

Description

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).

AI-Powered Analysis

AILast updated: 10/09/2025, 05:56:42 UTC

Technical Analysis

CVE-2025-7526 is a critical security vulnerability classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, i.e., Path Traversal) found in the WP Travel Engine – Tour Booking Plugin for WordPress. This plugin, widely used for managing tour bookings and operator software, contains a flaw in the set_user_profile_image function where file path validation is insufficient. This flaw allows unauthenticated attackers to craft requests that manipulate file paths, enabling arbitrary file deletion on the server. Because the vulnerability does not require authentication or user interaction, it can be exploited remotely by anyone with network access to the vulnerable WordPress instance. The ability to delete arbitrary files, including critical configuration files like wp-config.php, can lead to remote code execution by destabilizing the application or enabling attackers to upload malicious code or gain further access. The vulnerability affects all versions up to and including 6.6.7 of the plugin. The CVSS v3.1 score of 9.8 indicates a critical severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. Although no known exploits have been reported in the wild yet, the nature of the vulnerability makes it a prime target for attackers aiming to compromise WordPress sites. The lack of available patches at the time of disclosure increases the urgency for organizations to apply mitigations or monitor for suspicious activity. This vulnerability highlights the risks of inadequate input validation in web applications, especially those handling file operations.

Potential Impact

For European organizations, the impact of CVE-2025-7526 can be severe. Many businesses in Europe rely on WordPress plugins like WP Travel Engine to manage online tour bookings, making them attractive targets for attackers seeking to disrupt operations or steal sensitive data. Successful exploitation can lead to deletion of critical files, causing website downtime, loss of customer trust, and potential data breaches. Remote code execution following file deletion can result in full server compromise, enabling attackers to deploy ransomware, steal intellectual property, or pivot to other internal systems. The tourism sector, a significant part of several European economies, could face operational disruptions, financial losses, and reputational damage. Additionally, regulatory compliance risks arise under GDPR if personal data is exposed or systems are compromised. The ease of exploitation and lack of authentication requirements mean that attackers can rapidly target vulnerable sites at scale, increasing the threat landscape for European entities using this plugin.

Mitigation Recommendations

1. Immediate upgrade: Apply any available patches from the WP Travel Engine vendor as soon as they are released. Monitor vendor communications closely. 2. Temporary workarounds: If patches are unavailable, disable the vulnerable plugin or restrict access to the set_user_profile_image function via web server rules or application firewalls. 3. Input validation: Implement additional server-side validation to sanitize and restrict file path inputs, preventing traversal sequences such as '../'. 4. File system permissions: Harden file and directory permissions to limit the plugin's ability to delete critical files, ensuring the web server user has minimal privileges. 5. Monitoring and detection: Deploy file integrity monitoring to detect unexpected file deletions or modifications, and configure logging to capture suspicious requests targeting the vulnerable endpoint. 6. Web Application Firewall (WAF): Use a WAF to block malicious payloads attempting path traversal attacks against the plugin. 7. Incident response readiness: Prepare to respond rapidly to any signs of exploitation, including backups and recovery plans to restore deleted files. 8. Network segmentation: Isolate WordPress servers from critical internal networks to limit lateral movement if compromise occurs. 9. Regular security audits: Conduct periodic vulnerability assessments and penetration tests focusing on WordPress plugins and custom code.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-07-12T08:37:47.770Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68e74b345132fb26fe2091f7

Added to database: 10/9/2025, 5:42:12 AM

Last enriched: 10/9/2025, 5:56:42 AM

Last updated: 10/9/2025, 10:10:37 AM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats