PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-2437 wptravelengine CVE debrief

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. This vulnerability is due to insufficient input sanitization and output escaping on user-supplied attributes. Authenticated attackers with contributor-level access and above can inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This issue affects users of WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress, version 6.7.5 or earlier.

Vendor
wptravelengine
Product
WP Travel Engine – Tour Booking Plugin – Tour Operator Software
CVSS
MEDIUM 6.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-04
Original CVE updated
2026-07-24
Advisory published
2026-04-04
Advisory updated
2026-07-24

Who should care

Users of WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress, version 6.7.5 or earlier, should be aware of this vulnerability and take necessary actions to protect their applications. This includes administrators, security teams, and operators who manage WordPress installations with this plugin.

Technical summary

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. This is due to insufficient input sanitization and output escaping on user-supplied attributes. An authenticated attacker with contributor-level access and above can inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability requires authenticated access and can lead to Cross-Site Scripting attacks.

Defensive priority

Medium priority, as the vulnerability requires authenticated access and can lead to Cross-Site Scripting attacks.

Recommended defensive actions

  • Update WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin to a version beyond 6.7.5.
  • Implement input validation and output encoding for user-supplied attributes.
  • Monitor for suspicious activity and implement Content Security Policy (CSP) to mitigate Cross-Site Scripting attacks.
  • Restrict access to the plugin's shortcode functionality to prevent unauthorized users from injecting malicious scripts.
  • Regularly review and update the plugin to ensure the latest security patches are applied.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

The CVE record was published on 2026-04-04T09:16:20.003Z and was last modified on 2026-07-24T22:10:00.140Z. The NVD entry is currently Deferred. Evidence is limited to CVE and NVD information. Defenders should verify affected product deployments and review official advisories.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-2437 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-2437

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-2437 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-2437

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://plugins.trac.wordpress.org/changeset/3467196/wp-travel-engine/tags/6.7.6/includes/class-wp-travel-engine-custom-shortcodes.php

    [email protected]

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.