CVE-2025-13801Public exploitNetwork attack vectorHinoki check available

Unauthenticated file disclosure via log path traversal

Published Jan 7, 2026 · Updated Jan 7, 2026

Path traversal in Yoco Payments 3.9.0 and earlier allows remote attackers to read arbitrary server files through a public REST endpoint. The /wp-json/yoco/logs callback passes the file parameter directly to file_exists() and file_get_contents() under WC_LOG_DIR, while a substring check for yoco fails to constrain the canonical path. The route’s permit callback always returns true, so no authentication or user interaction is required; traversal can expose configuration files and credentials without modifying data or interrupting service.

CVSS severity7.5
High
EPSS probability1.87%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Path traversal in Yoco Payments 3.9.0 and earlier allows remote attackers to read arbitrary server files through a public REST endpoint. The /wp-json/yoco/logs callback passes the file parameter directly to file_exists() and file_get_contents() under WC_LOG_DIR, while a substring check for yoco fails to constrain the canonical path. The route’s permit callback always returns true, so no authentication or user interaction is required; traversal can expose configuration files and credentials without modifying data or interrupting service.

The record

CVE
CVE-2025-13801
Published
Jan 7, 2026
Updated
Jan 7, 2026
Vendor
Yoco
Product
Yoco Payments
Classifications
CWE-22, T1005
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 7, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 7, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=* <=3.8.8

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Yoco · Yoco Paymentsversion=* <=3.8.8

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
T1005Data from Local System

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo