CVE-2026-9231

7.5

WordPress · WP Travel Engine – Tour Booking Plugin – Tour Operator Software

The WP Travel Engine plugin for WordPress is vulnerable to Local File Inclusion via the wte_get_template function, allowing authenticated contributors to execute arbitrary PHP code.

Executive summary

A high-severity local file inclusion vulnerability in the WP Travel Engine plugin for WordPress allows authenticated attackers to execute arbitrary PHP code on the host server.

Vulnerability

This is a local file inclusion (CWE-98) flaw within the wte_get_template function. Authenticated users with contributor-level access or higher can manipulate this function to include and execute arbitrary PHP files located on the server.

Business impact

Successful exploitation permits an attacker to achieve remote code execution, which can lead to complete site compromise, unauthorized database access, and data exfiltration. Given the CVSS score of 7.5, this vulnerability represents a significant risk to the integrity and availability of the WordPress environment, especially for sites that allow user contributions.

Remediation

Immediate Action: Update the WP Travel Engine plugin to version 6.8.1 or later, as identified in the vendor changeset.

Proactive Monitoring: Audit WordPress user accounts to ensure only trusted individuals hold contributor-level permissions or higher, and monitor server logs for unusual file inclusion patterns or unexpected PHP execution requests.

Compensating Controls: Implement a Web Application Firewall (WAF) to block requests containing directory traversal sequences or suspicious path injection attempts directed at the affected plugin endpoints.

Exploitation status

Public Exploit Available: No (exploit_available unknown).

Analyst recommendation

This vulnerability poses a substantial risk to server security due to the potential for arbitrary code execution. Administrators should prioritize updating the WP Travel Engine plugin to the latest patched version immediately to eliminate the underlying flaw and prevent unauthorized access by privileged users.

More WordPress CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by 0xQRx, per the CVE Program record.