Travelpayouts
Avoid: Travelpayouts is closed on wordpress.org and no longer gets updates.
Capped at 10: the plugin is closed on wordpress.org.
| Ownership | 100 |
|---|---|
| Maintenance | 10 |
| Security | 95 |
| Support | No data |
| Reputation | No data |
Quick answers
- Is Travelpayouts still maintained?
- No. Closed on wordpress.org on 28 Oct 2026. 28 Oct 2026 · wordpress.org
- Who owns Travelpayouts, and has it changed hands?
- Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist. 3 Nov 2026 · SVN log
- Was Travelpayouts removed from wordpress.org?
- Yes. Closed on 28 Oct 2026, reason: reason not stated. 28 Oct 2026 · wordpress.org
- Is Travelpayouts safe?
- 5 known vulnerabilities, all fixed (latest in 1.2.4). Not on the exploited list. 29 Jan 2026 · Wordfence Intelligence
- Is the latest Travelpayouts update safe to install?
- Not enough data. No release date on record for the current version. Release history
Active signals
Facts we detected, with links to the source.
- WarningCLS-1Closed on wordpress.org on 28 Oct 2026, reason: reason not stated. Replace this plugin. It no longer receives updates from wordpress.org.28 Oct 2026Evidence
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
No ownership change recorded. Commit history is collected for plugins with 1,000+ installs or on a watchlist.
Maintenance
- Last release
- not recorded
- Releases, 24 months
- 0
- Tested up to
- not stated vs 7.1
- Requires PHP
- not stated supported 8.2+
Release history builds as we see new versions.
Reputation
Last 90 days: no reviews.
Security record
1 vulnerability in 24 months (5 on record), patched (latest fixed in 1.2.4).
Show 5 patched vulnerabilities
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 29 Jan 2026 | Travelpayouts <= 1.2.3 - Missing Authorization | 4.3 | <= 1.2.3 | 1.2.4 | n/a |
| 28 Feb 2024 | Travelpayouts: All Travel Brands in One Place <= 1.1.16 - Open Redirect | 6.1 | <= 1.1.16 | 1.1.17 | n/a |
| 26 Jan 2024 | Travelpayouts <= 1.1.12 - Cross-Site Request Forgery to Settings Import | 4.3 | <= 1.1.12 | 1.1.13 | n/a |
| 23 Jan 2024 | Travelpayouts <= 1.1.13 - Reflected Cross-Site Scripting | 6.1 | <= 1.1.13 | 1.1.14 | n/a |
| 13 Sep 2021 | Travelpayouts <= 1.0.16 - Cross-Site Request Forgery | 8.8 | <= 1.0.16 | 1.0.17 | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
Fewer than 10 active installs. History builds with each weekly snapshot.
Momentum history builds with each snapshot.
Healthier alternatives
Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.
No healthier plugin in the same category yet.
Facts
| Version | not stated |
|---|---|
| Author | not stated |
| Added | not stated |
| Last updated | not stated |
| Active installs | Fewer than 10 |
| Requires WordPress | not stated |
| Tested up to | not stated |
| Requires PHP | not stated |
| Category | E-commerce & Shopping |
| Tags | not stated |
Questions
Is Travelpayouts still maintained?
No. Closed on wordpress.org on 28 Oct 2026.
Who owns Travelpayouts, and has it changed hands?
Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist.
Was Travelpayouts removed from wordpress.org?
Yes. Closed on 28 Oct 2026, reason: reason not stated.
Is Travelpayouts safe?
5 known vulnerabilities, all fixed (latest in 1.2.4). Not on the exploited list.
Is the latest Travelpayouts update safe to install?
Not enough data. No release date on record for the current version.