CVE-2026-2437 MEDIUM

CVE-2026-2437: WP Travel Engine - Travel and Tour Booking Plugin <= 6.7.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via wte_trip_tax Shortcode

Vendor Wptravelengine
Product WP Travel Engine – Tour Booking Plugin – Tour Operator Software
Weakness CWE-79 · XSS
Published April 4, 2026
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wte_trip_tax' shortcode in all versions up to, and including, 6.7.5 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Explanation of Vulnerability in Simple Terms

02Summary

WP Travel Engine versions up to 6.7.5 contain a stored cross-site scripting (XSS) vulnerability. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other users, including site administrators. The vulnerability affects the plugin's scope across multiple components, allowing attackers to steal session tokens, modify site content, or perform actions on behalf of victims.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers and steal their session data or perform actions as them.

Potential impact on your site

04Site Impact

Authenticated attackers can compromise admin accounts, deface content, or steal visitor data without victims' knowledge.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account on the site; no user interaction required from victims.

Key dates

06Disclosure timeline

April 4, 2026 CVE published
April 8, 2026 Record updated