WP Travel Engine · Security record
Is WP Travel Engine safe?
No known vulnerability affects the current version (6.8.10). 25 issues were found in earlier versions and fixed, the latest disclosed on Aug 15, 2026.
Checked 3 days ago against the WPVulnerability database, for version 6.8.10.
How it’s looked after
- Last release
- Oct 13, 2026 (3 weeks ago)
- Releases in the last year
- 25
- Tested up to
- WordPress 7.1.4
- Support resolved
- 1 of 1 threads in two months
- Active installs
- 20K+
25 known vulnerabilities
- 5 critical
- 8 high
- 6 medium
- 6 not rated
None affects the current version.
Disclosed each year
- 20211
- 20223
- 20231
- 20245
- 20256
- 20269
Every known vulnerability in WP Travel Engine
Newest first, with any that affect the current version at the top.
Fixed in 6.8.1 · CVE-2026-9231 · Aug 15, 2026 · Wordfence
Fixed in 6.8.5 · CVE-2026-16737 · Aug 12, 2026 · Wordfence
Fixed in 6.8.2 · CVE-2026-12501 · Aug 6, 2026 · CVE
- high
Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'booking_id' Parameter
Fixed in 6.8.5 · CVE-2026-17087 · Aug 5, 2026 · Wordfence
Fixed in 6.8.1 · CVE-2026-10834 · Jul 7, 2026 · CVE
Fixed in 6.8.2 · CVE-2026-12500 · Jun 5, 2026 · Wordfence
Fixed in 6.7.11 · CVE-2026-49078 · Jun 4, 2026 · Wordfence
Fixed in 6.8.0 · CVE-2026-49770 · Jun 4, 2026 · Wordfence
Fixed in 6.7.6 · CVE-2026-2437 · Apr 3, 2026 · Wordfence
Fixed in 6.6.8 · CVE-2025-7634 · Oct 8, 2025 · Wordfence
Fixed in 6.6.8 · CVE-2025-7526 · Oct 8, 2025 · Wordfence
Fixed in 6.5.2 · CVE-2025-5282 · Jun 12, 2025 · Wordfence
Fixed in 6.5.2 · CVE-2025-49308 · Jun 5, 2025 · Wordfence
Fixed in 6.3.6 · CVE-2025-30870 · Mar 27, 2025 · Wordfence
Fixed in 6.3.6 · CVE-2025-30871 · Mar 27, 2025 · Wordfence
Fixed in 6.2.2 · CVE-2024-10606 · Nov 22, 2024 · Wordfence
Fixed in 5.9.2 · CVE-2024-37944 · Jul 10, 2024 · Wordfence
Fixed in 5.8.1 · CVE-2024-32798 · Apr 22, 2024 · Wordfence
Fixed in 5.8.0 · CVE-2024-30504 · Mar 28, 2024 · Wordfence
- critical
Unauthenticated SQL Injection
Fixed in 5.8.0 · CVE-2024-30502 · Mar 28, 2024 · Wordfence
Fixed in 5.7.5 · CVE-2023-33999 · Jul 18, 2023 · WPScan
Fixed in 5.3.8 · CVE-2022-4974 · Mar 4, 2022 · Wordfence
Fixed in 5.3.8 · Feb 28, 2022 · Patchstack
Fixed in 5.3.8 · Feb 28, 2022 · Patchstack
Fixed in 5.3.8 · CVE-2021-24680 · Dec 1, 2021 · Wordfence
Questions about WP Travel Engine’s security
Is WP Travel Engine safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep WP Travel Engine updated: most attacks target sites that haven’t updated.
Does WP Travel Engine have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 25 older issues, fixed in earlier versions, so keep WP Travel Engine up to date.
Is WP Travel Engine still maintained?
Yes. Its last release was 3 weeks ago. Its authors resolved 1 of the 1 support threads opened in the last two months.
Is WP Travel Engine compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.