Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Travelpayouts · Security record

Is Travelpayouts safe?

One known vulnerability affects the current version (1.3.1), and it has no fix yet.

Checked 2 days ago against the WPVulnerability database, for version 1.3.1.

How it’s looked after

Last release
Oct 15, 2026 (3 weeks ago)
Releases in the last year
5
Tested up to
WordPress 7.1.3
Support resolved
0 of 1 threads in two months
Active installs
6K+

6 known vulnerabilities

  • 1 high
  • 3 medium
  • 2 not rated

1 affects the current version. 1 has no fix yet.

Disclosed each year

  • 20211
  • 20243
  • 20261

Every known vulnerability in Travelpayouts

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

Questions about Travelpayouts’s security

Is Travelpayouts safe to use?

Yes: 1 known vulnerability affects version 1.3.1, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.

Does Travelpayouts have known security vulnerabilities?

Yes: 1 known vulnerability affects version 1.3.1, according to WPVulnerability’s database.

Is Travelpayouts still maintained?

Yes. Its last release was 3 weeks ago. Its authors resolved 0 of the 1 support threads opened in the last two months.

Is Travelpayouts compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.3, 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.