CVE-2021-24680

WP Travel Engine <= 5.3.0 - Editor+ Stored Cross-Site Scripting

2021-12-01 00:00
Huy Nguyen

Strategic Overview

Status
Patched in 5.3.1
Affected Version
<= 5.3.0
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24680
View all WP Travel Engine – Tour Booking Plugin – Tour Operator Software vulnerabilities

At a glance

CVE-2021-24680 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Travel Engine WordPress plugin, affecting versions <= 5.3.0. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). The issue is fixed in version 5.3.1; sites on affected versions should update now. Disclosed December 2021, reported by Huy Nguyen.

Vulnerability Overview

The WP Travel Engine WordPress plugin before 5.3.1 does not escape the Description field in the Trip Destination/Activities/Trip Type and Pricing Category pages, allowing users with a role as low as editor to perform Stored Cross-Site Scripting attacks, even when the unfiltered_html capability is disallowed

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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WP Travel Engine <= 5.3.0 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP Travel Engine the fix is 5.3.1: builds <= 5.3.0 are affected, anything from 5.3.1 onward is not.

Remediation

Update to version 5.3.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Travel Engine: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Travel Engine 5.3.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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