dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-13801

HIGH · 7.5 CVSS v3.1 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Yoco Payments WordPress plugin contains a Path Traversal vulnerability in versions up to 3.9.0, allowing unauthenticated attackers to manipulate the file parameter to read arbitrary files on the server. This occurs because the plugin does not properly sanitize or validate user-supplied file paths before passing them to file read operations, enabling directory traversal sequences like '../' to access sensitive files outside the intended directory.

MitigationUpgrade to version 3.9.1 or later which contains the security fix. If immediate upgrade is not possible, consider disabling the plugin until patched. Additionally, ensure the web server runs with minimal file system permissions to limit the impact of any file read vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Yoco Payments plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Yoco Payments and read the version number displayed. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/yoco-payments/) for the Version header in the file comment or any version constant.
    Affected if The displayed version is 3.9.0 or lower.
  2. Confirm the plugin is active
    In WordPress admin, verify that Yoco Payments appears in the list of active plugins. An inactive plugin may not expose the vulnerable endpoint.
    Affected if The plugin is active and version is 3.9.0 or lower.
  3. Identify the vulnerable file read functionality
    Search the plugin directory (wp-content/plugins/yoco-payments/) for code that handles a file parameter and performs file read operations. Look for functions like file_get_contents, fopen, readfile, or similar that accept user input without proper sanitization.
    Affected if The plugin code contains file read operations that accept a file parameter without validating for directory traversal sequences like '../'.
  4. Test for directory traversal accessibility
    If you can safely do so without causing harm, examine whether an HTTP request to the plugin's endpoint can include a file parameter with '../' sequences to access files outside the intended directory. This check requires access to server logs or the ability to observe the application's response.
    Affected if The plugin accepts and processes file paths containing '../' sequences, allowing access to files outside the intended directory.

You are affected if the Yoco Payments plugin is active and the installed version is 3.9.0 or lower, since the vulnerability allows unauthenticated path traversal via the file parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 3.9.1 or later which contains the security fix. If immediate upgrade is not possible, consider disabling the plugin until patched. Additionally, ensure the web server runs with minimal file system permissions to limit the impact of any file read vulnerability.

Recommended fix Moderate confidence

Any version higher than 3.9.0 (check wordpress.org for latest stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Yoco Payments plugin
  4. Check if the current version is 3.9.0 or lower
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, navigate to Plugins > Add New > Upload and upload the latest version from wordpress.org/plugins/yoco-payments/
  7. After update, verify the plugin version is higher than 3.9.0

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13801 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13801 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data