HomeWordPress vulnerabilitiesTravelpayouts
Travelpayouts vulnerabilities
Travelpayouts has 3 known vulnerabilities in this database. The most recent published record is dated 15 May 2025.
- Known vulnerabilities
- 3
- Active installs
- 6,000+
- Latest version
- 1.2.3
- Last updated
- 4 Aug 2026
- Most recent
- 15 May 2025
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 |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2023-5932 | Medium 4.8 | Before 1.1.14 | Fixed in 1.1.14 | 15 May 2025 |
| Cross-site request forgery (CSRF) CVE-2023-5934 | High 7.3 | Before 1.1.13 | Fixed in 1.1.13 | 15 May 2025 |
| Open redirect CVE-2024-0337 | Medium 6.1 | Before 1.1.17 | Fixed in 1.1.17 | 20 Mar 2024 |
Read the published descriptions
- CVE-2023-5932, 15 May 2025
- The Travelpayouts: All Travel Brands in One Place WordPress plugin before 1.1.14 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin CVE record
- CVE-2023-5934, 15 May 2025
- The Travelpayouts: All Travel Brands in One Place WordPress plugin before 1.1.13 does not have CSRF check in place when importing settings from the v1, which could allow attackers to make a logged in admin update some settings via a CSRF attack CVE record
- CVE-2024-0337, 20 Mar 2024
- The Travelpayouts: All Travel Brands in One Place WordPress plugin through 1.1.15 is vulnerable to Open Redirect due to insufficient validation on the travelpayouts_redirect variable. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action. CVE record
What to do if you run Travelpayouts
If you run Travelpayouts, 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 Travelpayouts vulnerabilities
Free. We email you when a new vulnerability is published for Travelpayouts, 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.