CVE-2024-30502

WP Travel Engine <= 5.7.9 - Unauthenticated SQL Injection

2024-03-28 00:00
beluga

Strategic Overview

Status
Patched in 5.8.0
Affected Plugin
WP Travel Engine – Tour Booking Plugin – Tour Operator Software
Affected Version
<= 5.7.9
CVSS
10.0Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2024-30502
View all WP Travel Engine – Tour Booking Plugin – Tour Operator Software vulnerabilities

At a glance

CVE-2024-30502 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Travel Engine WordPress plugin, affecting versions <= 5.7.9. It carries a CVSS score of 10.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.8.0; sites on affected versions should update now. Disclosed March 2024, reported by beluga.

Vulnerability Overview

The WP Travel Engine plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 5.7.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in WP Travel Engine <= 5.7.9 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WP Travel Engine the fix is 5.8.0: builds <= 5.7.9 are affected, anything from 5.8.0 onward is not.

Remediation

Update to version 5.8.0, 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.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-30502https://www.wordfence.com/threat-intel/vulnerabilities/id/659fcb95-9041-443e-9b75-0d2f8c6108aahttps://nvd.nist.gov/vuln/detail/CVE-2024-30502

Related records

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