HomeWordPress vulnerabilitiesWP Travel
WP Travel vulnerabilities
WP Travel has 8 known vulnerabilities in this database. The most recent published record is dated 9 Sep 2026.
- Known vulnerabilities
- 8
- Active installs
- 3,000+
- Latest version
- 12.0.4
- Last updated
- 21 Sep 2026
- Most recent
- 9 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-18042 | Medium 5.3 | Before 12.0.2 | Fixed in 12.0.2 | 9 Sep 2026 |
| Broken access control CVE-2026-13144 | Low 3.7 | Before 12.0.2 | Fixed in 12.0.2 | 9 Sep 2026 |
| Broken access control CVE-2026-13146 | Low 3.7 | Before 12.0.2 | Fixed in 12.0.2 | 9 Sep 2026 |
| Security weakness CVE-2026-13143 | Medium 5.3 | Before 11.8.1 | Fixed in 11.8.1 | 30 Jul 2026 |
| Broken access control CVE-2026-13145 | Medium 4.3 | Before 11.8.1 | Fixed in 11.8.1 | 30 Jul 2026 |
| Broken access control CVE-2026-11868 | Medium 5.3 | Before 11.7.1 | Fixed in 11.7.1 | 20 Jul 2026 |
| SQL injection CVE-2024-12067 | Medium 6.5 | Up to 10.0.0 | Fixed in a later version (latest 12.0.4) | 9 Jan 2025 |
| Cross-site request forgery (CSRF) CVE-2021-4389 | Medium 4.3 | Before 4.4.7 | Fixed in 4.4.7 | 1 Jul 2023 |
Read the published descriptions
- CVE-2026-18042, 9 Sep 2026
- The WP Travel WordPress plugin before 12.0.2 does not verify that the requester is authorized to act on the booking targeted by one of its front-end payment-message handlers, allowing unauthenticated attackers to cancel the payment on any customer's booking. CVE record
- CVE-2026-13144, 9 Sep 2026
- The WP Travel WordPress plugin before 12.0.2 does not properly verify that the requester is authorized to modify the targeted booking on one branch of its bank-deposit handler, allowing an unauthenticated attacker who knows the target customer's email address to reset that customer's booking payment to an unpaid state and wipe its stored deposit-reconciliation data. CVE record
- CVE-2026-13146, 9 Sep 2026
- The WP Travel WordPress plugin before 12.0.2 does not properly verify that the requester owns the booking targeted by its bank-deposit slip submission, allowing an unauthenticated attacker who knows the target customer's email address to change that customer's booking payment state and attach a file to it. CVE record
- CVE-2026-13143, 30 Jul 2026
- The WP Travel WordPress plugin before 11.8.1 does not verify PayPal Instant Payment Notifications through the PayPal post-back handshake before marking a booking paid, allowing unauthenticated attackers to forge a notification that flips an arbitrary pending booking to a paid and booked state at an attacker-chosen amount. CVE record
- CVE-2026-13145, 30 Jul 2026
- The WP Travel WordPress plugin before 11.8.1 does not verify that the booking requested on its customer account dashboard belongs to the current user, allowing any logged-in user to read another customer's booking details, including billing address information, by supplying an arbitrary booking identifier. CVE record
- CVE-2026-11868, 20 Jul 2026
- The WP Travel WordPress plugin before 11.7.1 does not perform capability or ownership checks on its booking cancellation action, which is also exposed to unauthenticated users, allowing them to cancel arbitrary bookings on the site. CVE record
- CVE-2024-12067, 9 Jan 2025
- The WP Travel - Ultimate Travel Booking System, Tour Management Engine plugin for WordPress is vulnerable to SQL Injection via the 'booking_itinerary' parameter of the 'wptravel_get_booking_data' function in all versions up to, and including, 10.0.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2021-4389, 1 Jul 2023
- The WP Travel plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.4.6. This is due to missing or incorrect nonce validation on the save_meta_data() function. This makes it possible for unauthenticated attackers to save metadata for travel posts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
What to do if you run WP Travel
If you run WP Travel, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Travel vulnerabilities
Free. We email you when a new vulnerability is published for WP Travel, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.