CVE-2023-5934: The Travelpayouts: All Travel Brands in One Place WordPress plugin before 1.1.13 does not have CSRF check in p

Q: How do I fix CVE-2023-5934?

travelpayouts: upgrade to 1.1.13. Exact commands for each OS are on this page.

Q: Is CVE-2023-5934 being exploited?

CVE-2023-5934 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2023-5934 affect?

CVE-2023-5934 affects travelpayouts. Severity is high (CVSS 7.3). 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 at

Q: How urgent is CVE-2023-5934?

Priority 40/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.3REMOTEUPGRADE

CVE-2023-5934 is a high-severity flaw (CVSS 7.3) affecting travelpayouts. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 84%)
CISA exploited list	No
Weakness	CWE-352
Published	2025-05-15
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: travelpayouts

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-15 20:15 UTCPublished CVE record published
2026-06-17 06:49 UTCUpdated Record last modified

travelpayouts travelpayouts UPGRADE

Affected: < 1.1.13

Fixed in: 1.1.13

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy travelpayouts || rpm -q travelpayouts || travelpayouts --version

2. UPGRADE to 1.1.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade travelpayouts

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade travelpayouts

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-5934?

travelpayouts: upgrade to 1.1.13. Exact commands for each OS are on this page.

Is CVE-2023-5934 being exploited?

CVE-2023-5934 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-5934 affect?

CVE-2023-5934 affects travelpayouts. Severity is high (CVSS 7.3). 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 at

How urgent is CVE-2023-5934?

Priority 40/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-0337 MEDIUM 6.1 UPGRADE The Travelpayouts: All Travel Brands in One Place WordPress plugin through 1.1.15 is vulnerable to Open Redire
CVE-2023-5932 MEDIUM 4.8 UPGRADE The Travelpayouts: All Travel Brands in One Place WordPress plugin before 1.1.14 does not sanitise and escape

References

← Back to latest CVEs