# CVE-2025-13801: Yoco Payments <= 3.9.0 - Unauthenticated Arbitrary File Read

> Unauthenticated attackers can read arbitrary files on the server via path traversal in the Yoco Payments WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-p4xw-96rj-wp46

## What is CVE-2025-13801?

CVE-2025-13801 is a high-severity path traversal vulnerability in yocoadmin Yoco Payments, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Yoco Payments plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 3.9.0 via the file parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-13801?


## How do I fix CVE-2025-13801?

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

## Is CVE-2025-13801 being exploited?

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

Public exploit code:

- Yoco Payments <= 3.8.8 - Path Traversal (nuclei): http/cves/2025/CVE-2025-13801.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13801 and fix it if it is affected.

What it is: CVE-2025-13801 is a high-severity path traversal vulnerability in yocoadmin Yoco Payments, published on 7 Jan 2026. 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-2025-13801 exists.

Affected product: yocoadmin Yoco Payments. 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-2025-13801/ (Markdown: https://insights.sbomify.com/CVE-2025-13801/index.md)
```

## Sources

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

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