Is CVE-2026-2437 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-2437 being exploited in the wild.

How severe is CVE-2026-2437?

Medium severity, with a CVSS score of 6.4, published 4 April 2026.

Which products and versions are affected?

WP Travel Engine up to, and including, 6.7.5.

Is there a fix for CVE-2026-2437?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-2437 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-2437?

Check whether you run WP Travel Engine at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-2437: WP Travel Engine Stored XSS in wte_trip_tax shortcode

CVE-2026-2437 · Severity: medium · CVSS 6.4 · Published 2026-04-04

WP Travel Engine is a WordPress plugin used by tour operators to manage bookings and trip details. A security flaw allows users with contributor-level access or higher to inject malicious scripts into website pages. These scripts execute automatically when other users, including site administrators, view the affected pages, potentially leading to unauthorized actions or data theft.

Technologies: WP Travel Engine. Vendors: WP Travel Engine.

Quick answers

Is CVE-2026-2437 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-2437 being exploited in the wild.
How severe is CVE-2026-2437?: Medium severity, with a CVSS score of 6.4, published 4 April 2026.
Which products and versions are affected?: WP Travel Engine up to, and including, 6.7.5.
Is there a fix for CVE-2026-2437?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-2437 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-2437?: Check whether you run WP Travel Engine at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The WP Travel Engine plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) via the 'wte_trip_tax' shortcode. The root cause is insufficient input sanitization and output escaping on user-supplied attributes within the shortcode implementation. An authenticated attacker with contributor-level permissions or higher can exploit this by injecting arbitrary web scripts into a post or page. These scripts will execute in the context of any user's browser who visits the compromised page. The vulnerability is addressed in version 6.7.6.

Affected products

wptravelengine WP Travel Engine – Tour Booking Plugin – Tour Operator Software up to, and including, 6.7.5

Timeline

2026-04-04: disclosed
2026-04-04: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.