Overview
The WP Travel Engine – Tour Booking Plugin for WordPress, a popular tool used by tour operators, is vulnerable to unauthorized data loss due to a significant flaw in its delete_package() function. This vulnerability, labeled as CVE-2025-5282, allows unauthenticated attackers to delete arbitrary posts, posing a potential threat to system integrity and data confidentiality.
Vulnerability Summary
CVE ID: CVE-2025-5282
Severity: High (7.5 CVSS)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Unauthorized deletion of arbitrary posts, potential system compromise, and data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
WP Travel Engine – Tour Booking Plugin – Tour Operator Software Plugin for WordPress | Up to and including 6.5.1
How the Exploit Works
The vulnerability exists due to a missing capability check on the delete_package() function in the WP Travel Engine – Tour Booking Plugin. This lack of a capability check means that any user, authenticated or not, can send a request to delete any arbitrary post. In the hands of a malicious actor, this can lead to unauthorized data loss, system compromise, or data leakage.
Conceptual Example Code
Below is a conceptual example of how the vulnerability might be exploited using an HTTP request:
POST /wp-travel-engine/delete_package HTTP/1.1
Host: vulnerable-website.com
Content-Type: application/x-www-form-urlencoded
package_id=1234
In this example, `package_id` corresponds to the ID of the post or ‘package’ that the attacker wishes to delete. The server, due to the vulnerability, does not check if the user has the required permissions to delete the post, leading to unauthorized data loss.
Mitigation Guidance
Users of the affected plugin are strongly advised to apply the vendor’s patch at the earliest. In case the patch cannot be applied immediately, users should consider using a Web Application Firewall (WAF) or Intrusion Detection System (IDS) as a temporary mitigation measure. Prompt action is crucial to prevent potential system compromise or data leakage.

