Cyber Resilience

CVE-2025-1973

Path Traversal in Webtoffee Import Export Wordpress Users ≤ 2.6.3

Path Traversal
Published
22 March 2025
Modified
09 July 2025
Patch / advisory
View advisory
CVSS Score v3.1 4.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0069 50th percentile
Risk Priority 40 floored blend · peak EPSS

Summary

CVE-2025-1973 is a medium-severity Path Traversal (CWE-22) vulnerability in Webtoffee Import Export Wordpress Users. Its CVSS base score is 4.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 50th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

The Export and Import Users and Customers plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 2.6.2 via the download_file() function. This makes it possible for authenticated attackers, with Administrator-level access and above, to…

more

read the contents of arbitrary log files on the server, which can contain sensitive information.

CWE(s)
CWE-22

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-40384Same product class: CMS core
CVE-2024-52396Same product class: CMS core
CVE-2024-39406Same product class: CMS core
CVE-2024-10470Same product class: CMS core
CVE-2023-2688Same product class: CMS core
CVE-2025-1769Same vendor: Webtoffee
CVE-2025-24406Same product class: CMS core
CVE-2023-30451Same product class: CMS core
CVE-2026-21360Same product class: CMS core
CVE-2025-24605Same product class: CMS core

Affected Assets

webtoffee
import export wordpress users
≤ 2.6.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

SI-10 Information Input Validation good match

Input validation directly neutralizes special path elements before pathname construction occurs.

AC-6 Least Privilege partial match

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches path traversal via static/dynamic analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for safe file handling and canonicalization.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require least-privilege file access and directory isolation.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

A.8.3 Information access restriction partial match
mitigates

Information access restriction limits which files an application may read or write.

References