# CVE-2023-5934: Travelpayouts < 1.1.13 - Settings Update via CSRF

> Attackers can trick logged-in admins into updating plugin settings via CSRF, requiring an upgrade to the latest version.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-vcpp-7qvc-rxv7

## What is CVE-2023-5934?

CVE-2023-5934 is a high-severity vulnerability in Unknown Travelpayouts: All Travel Brands in One Place, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-5934?

It affects 1 product.


Products: Travelpayouts Travelpayouts.

## How do I fix CVE-2023-5934?

No fix has been published for CVE-2023-5934 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-5934 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5934 exists.

## Other vulnerabilities in Unknown Travelpayouts: All Travel Brands in One Place

- [CVE-2024-0337](https://insights.sbomify.com/CVE-2024-0337/): Travelpayouts <= 1.1.15 - Open Redirect (medium 6.1)
- [CVE-2023-5932](https://insights.sbomify.com/CVE-2023-5932/): Travelpayouts < 1.1.14 - Reflected XSS (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5934 and fix it if it is affected.

What it is: CVE-2023-5934 is a high-severity vulnerability in Unknown Travelpayouts: All Travel Brands in One Place, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5934 exists.

Affected product: Unknown Travelpayouts: All Travel Brands in One Place. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5934/ (Markdown: https://insights.sbomify.com/CVE-2023-5934/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5934
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5934
- OSV: https://osv.dev/vulnerability/CVE-2023-5934

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5934/
Summaries are generated and may contain mistakes; the official description above is the record.