Is WP Travel Engine safe?

No known vulnerability affects the current version (1.5.5). 2 issues were found in earlier versions and fixed, the latest disclosed on Sep 22, 2025.

Checked 1 day ago against the WPVulnerability database, for version 1.5.5.

How it’s looked after

Last release: Sep 9, 2026 (1 month ago)
Releases in the last year: 11
Tested up to: WordPress 7.1.4
Active installs: 10K+

2 known vulnerabilities

1 high
1 medium

None affects the current version.

Disclosed each year

20241
20251

Every known vulnerability in WP Travel Engine

Newest first, with any that affect the current version at the top.

medium
Authenticated (Contributor+) Stored Cross-Site Scripting
Fixed in 1.4.3 · CVE-2025-59574 · Sep 22, 2025 · Wordfence
high
Authenticated (Contributor+) Local File Inclusion
Fixed in 1.3.8 · CVE-2024-12272 · Dec 24, 2024 · 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 2 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 1 month ago. No support threads were 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 free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.