# CVE-2026-13145: WP Travel WordPress plugin IDOR in customer account dashboard

Source: https://junglewise.ai/threats/cve-2026-13145-wp-travel-wordpress-plugin-idor-in-customer-account-dashboard  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-30. Updated: 2026-07-30  
License: CC BY 4.0 with a link back

CVE-2026-13145 · Severity: info · CVSS 4.3 · Published 2026-07-30

WP Travel, a popular WordPress plugin for managing travel bookings, contains a security flaw that allows any registered user to view the private booking details of other customers. By simply changing a booking ID in their account dashboard, an attacker can access sensitive information such as billing addresses, order numbers, and booking dates. This could lead to the exposure of customer personally identifiable information (PII) and potential reputational damage for travel agencies using the software.

Technologies: [WP Travel](https://junglewise.ai/threats/technologies/wp-travel). Vendors: [WP Travel](https://junglewise.ai/threats/vendors/wp-travel).

## Quick answers

**Is CVE-2026-13145 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-13145 being exploited in the wild.

**How severe is CVE-2026-13145?** Informational severity, with a CVSS score of 4.3, published 30 July 2026.

**Which products and versions are affected?** WP Travel < 11.8.1.

**Is there a fix for CVE-2026-13145?** A patch was published on 2026-07-13: Fixed in version 11.8.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-13145 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-13145?** Check whether you run WP Travel 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 plugin for WordPress fails to implement proper authorization checks on the customer account dashboard. Specifically, the dashboard component (triggered by the [wp_travel_user_account] shortcode) does not verify if a requested 'detail_id' belongs to the currently logged-in user. An attacker with a low-privileged account (Subscriber+) can obtain a publicly available nonce and then supply an arbitrary booking identifier via the 'detail_id' parameter to retrieve sensitive PII, including billing street, city, postal code, and country. This is a classic Insecure Direct Object Reference (IDOR) vulnerability (CWE-639). The issue is resolved in version 11.8.1.

## Affected products

- WP Travel WP Travel < 11.8.1

## Timeline

- 2026-07-13: disclosed: Publicly published by WPScan
- 2026-07-30: advisory: NVD publication date
- 2026-07-13: patched: Fixed in version 11.8.1

## References

- [https://wpscan.com/vulnerability/f70172b6-0a55-4b99-8b3c-8170224938bb/](https://wpscan.com/vulnerability/f70172b6-0a55-4b99-8b3c-8170224938bb/)

## Related threats

- [WP Travel WordPress plugin IDOR in booking payment submission](https://junglewise.ai/threats/cve-2026-13146-wp-travel-wordpress-plugin-idor-in-booking-payment-submission)
- [WP Travel arbitrary booking payment reset via broken access control](https://junglewise.ai/threats/cve-2026-13144-wp-travel-arbitrary-booking-payment-reset-via-broken-access)
- [WP Travel payment bypass via forged PayPal IPN notification](https://junglewise.ai/threats/cve-2026-13143-wp-travel-payment-bypass-via-forged-paypal-ipn-notification)
- [WP Travel WordPress plugin unauthenticated booking cancellation](https://junglewise.ai/threats/cve-2026-11868-wp-travel-wordpress-plugin-unauthenticated-booking-cancellation)
- [WP Travel WP Travel blind SQL injection](https://junglewise.ai/threats/cve-2026-45218-wp-travel-wp-travel-blind-sql-injection)