Cyber Resilience

CVE-2024-10857

Tychesoftwares Product Input Fields For Woocommerce ≤ 2.0

Published
26 November 2024
Modified
09 July 2025
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0075 52th percentile
Risk Priority 54 floored blend · peak EPSS

Summary

CVE-2024-10857 is a medium-severity Path Traversal: '.../...//' (CWE-35) vulnerability in Tychesoftwares Product Input Fields For Woocommerce. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

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

EU & UK References

Vulnerability Data

The Product Input Fields for WooCommerce plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.9 via the handle_downloads() function due to insufficient file path validation/sanitization. This makes it possible for authenticated attackers, with…

more

Contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-13359Same product: Tychesoftwares Product Input Fields For Woocommerce
CVE-2025-2907Same product class: WordPress / CMS plugin
CVE-2023-41858Same product class: WordPress / CMS plugin
CVE-2023-2986Same product class: WordPress / CMS plugin
CVE-2023-44986Same product class: WordPress / CMS plugin
CVE-2023-41874Same product class: WordPress / CMS plugin
CVE-2023-0479Same product class: WordPress / CMS plugin
CVE-2025-2929Same product class: WordPress / CMS plugin
CVE-2024-9345Same product class: WordPress / CMS plugin
CVE-2025-22786Same product class: WordPress / CMS plugin

Affected Assets

tychesoftwares
product input fields for woocommerce
≤ 2.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly neutralizes path sequences so the traversal cannot be introduced or exploited.

Enforces access authorizations on the resulting pathname, blocking traversal attempts from succeeding.

Enforces information flow rules that stop unauthorized directory escapes via crafted paths.

Least privilege reduces the impact of any successful traversal by limiting accessible resources.

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-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that neutralize traversal sequences.

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.

finds

Security testing in development can detect path-traversal flaws before release.

prevents

Secure SDLC mandates input validation and path-handling controls that directly mitigate path traversal.

prevents

Application security requirements include rules for safe file-path construction and canonicalization.

prevents

Secure architecture principles require proper directory restrictions and input sanitization to prevent traversal.

prevents

Secure coding standards explicitly forbid unsafe path concatenation and mandate canonicalization routines.

mitigates

Information access restriction limits file reachability but does not address the input-validation flaw itself.

References