CVE-2024-32798

WP Travel Engine <= 5.8.0 - Unauthenticated Price Manipulation

2024-04-22 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 5.8.1
Affected Version
<= 5.8.0
CVSS
5.3Medium
Weakness type
CWE-472 · External Control of Assumed-Immutable Web Parameter
CVE
CVE-2024-32798
View all WP Travel Engine – Tour Booking Plugin – Tour Operator Software vulnerabilities

At a glance

CVE-2024-32798 is a medium-severity External Control of Assumed-Immutable Web Parameter vulnerability in the WP Travel Engine WordPress plugin, affecting versions <= 5.8.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.8.1; sites on affected versions should update now. Disclosed April 2024, reported by Ananda Dhakal.

Vulnerability Overview

The WP Travel Engine – Best Travel Booking WordPress Plugin plugin for WordPress is vulnerable to price manipulation in all versions up to, and including, 5.8.0. This is due to the plugin not properly validating a price. This makes it possible for unauthenticated attackers to manipulate the price of bookings.

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.

CWE-472: External Control of Assumed-Immutable Web Parameter

Reaching this weakness in WP Travel Engine <= 5.8.0 takes no account at all. External control of an assumed-immutable parameter means the code trusts a value it believes cannot be changed by the caller, when in fact the request carries it.

Editing that field changes the outcome of the operation, which on commerce plugins means altered prices or totals and on account flows means acting as another user. For WP Travel Engine the fix is 5.8.1: builds <= 5.8.0 are affected, anything from 5.8.1 onward is not.

Remediation

Update to version 5.8.1, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Travel Engine 5.8.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

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