CVE-2024-10606

WP Travel Engine <= 6.2.1 - Missing Authorization to Authenticated (Contributor+) Plugin Settings Update

2024-11-22 00:00
Noah Stead (TurtleBurg)

Strategic Overview

Status
Patched in 6.2.2
Affected Plugin
WP Travel Engine – Tour Booking Plugin – Tour Operator Software
Affected Version
<= 6.2.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-10606
View all WP Travel Engine – Tour Booking Plugin – Tour Operator Software vulnerabilities

At a glance

CVE-2024-10606 is a medium-severity Missing Authorization vulnerability in the WP Travel Engine WordPress plugin, affecting versions <= 6.2.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 6.2.2; sites on affected versions should update now. Disclosed November 2024, reported by Noah Stead (TurtleBurg).

Vulnerability Overview

The WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wpte_onboard_save_function_callback() function in all versions up to, and including, 6.2.1. This makes it possible for authenticated attackers, with contributor-level access and above, to modify several settings that could have an impact such as lost revenue and page updates.

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 interaction from a victim user.

CWE-862: Missing Authorization

WP Travel Engine <= 6.2.1 carries this weakness at wpte_onboard_save_function_callback(), and reaching it takes an account at Contributor level or above. 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.2.2: builds <= 6.2.1 are affected, anything from 6.2.2 onward is not.

Remediation

Update to version 6.2.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Travel Engine 6.2.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-2024-10606https://www.wordfence.com/threat-intel/vulnerabilities/id/c91d1ec0-0430-4ddd-b6b1-25af0b5cea9dhttps://nvd.nist.gov/vuln/detail/CVE-2024-10606

Related records

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