# CVE-2026-13144: WP Travel arbitrary booking payment reset via broken access control

Source: https://junglewise.ai/threats/cve-2026-13144-wp-travel-arbitrary-booking-payment-reset-via-broken-access  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-09. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-13144 · Severity: low · CVSS 3.7 · Published 2026-09-09

WP Travel is a WordPress plugin for managing travel bookings and payments. This vulnerability allows an unauthenticated attacker to reset any customer's booking payment from paid to unpaid state and erase deposit reconciliation records, using only the victim's email address and a publicly-available security token. This could enable payment fraud, refund manipulation, or disruption of travel business operations.

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-13144 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-13144 being exploited in the wild.

**How severe is CVE-2026-13144?** Low severity, with a CVSS score of 3.7, published 9 September 2026.

**Which products and versions are affected?** WP Travel before 12.0.2.

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

**How is CVE-2026-13144 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-13144?** 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 plugin's bank-deposit payment handler fails to verify that the requester has authorization to modify a specific booking, instead only validating the presence of a valid nonce and matching email address. An attacker can exploit this broken access control to modify arbitrary bookings by obtaining a wp_travel_security nonce from any public page (valid for all bookings due to constant action binding), enumerating booking IDs, and sending a POST request with the target customer's email. The vulnerability requires no authentication or session cookies. Patches are available in version 12.0.2 and later.

## Affected products

- WP Travel WP Travel before 12.0.2

## Timeline

- 2026-09-07: disclosed
- 2026-09-09: patched: Fixed in version 12.0.2

## References

- [https://wpscan.com/vulnerability/6ffdaa34-83fd-4a05-bf36-071b17f280c4/](https://wpscan.com/vulnerability/6ffdaa34-83fd-4a05-bf36-071b17f280c4/)

## 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 WordPress plugin IDOR in customer account dashboard](https://junglewise.ai/threats/cve-2026-13145-wp-travel-wordpress-plugin-idor-in-customer-account-dashboard)
- [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)