CVE-2025-5282

WP Travel Engine <= 6.5.1 - Missing Authorization to Unauthenticated Arbitrary Post Deletion

2025-06-12 00:00
mikemyers

Strategic Overview

Status
Patched in 6.5.2
Affected Plugin
WP Travel Engine – Tour Booking Plugin – Tour Operator Software
Affected Version
<= 6.5.1
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-5282
View all WP Travel Engine – Tour Booking Plugin – Tour Operator Software vulnerabilities

At a glance

CVE-2025-5282 is a high-severity Missing Authorization vulnerability in the WP Travel Engine WordPress plugin, affecting versions <= 6.5.1. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 6.5.2; sites on affected versions should update now. Disclosed June 2025, reported by mikemyers.

Vulnerability Overview

The WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the delete_package() function in all versions up to, and including, 6.5.1. This makes it possible for unauthenticated attackers to delete arbitrary posts.

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

CWE-862: Missing Authorization

WP Travel Engine <= 6.5.1 carries this weakness at delete_package(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Travel Engine the fix is 6.5.2: builds <= 6.5.1 are affected, anything from 6.5.2 onward is not.

Remediation

Update to version 6.5.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Travel Engine 6.5.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-5282https://www.wordfence.com/threat-intel/vulnerabilities/id/ebc8d724-3936-42d8-8850-bc330c5221dchttps://nvd.nist.gov/vuln/detail/CVE-2025-5282

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C