Cyber Resilience

CVE-2023-35840

Path Traversal in Std42 Elfinder ≤ 2.1.62

Public PoCPath Traversal
Published
19 June 2023
Modified
12 December 2024
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:N/I:H/A:N
EPSS Score 0.019 78th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2023-35840 is a medium-severity Path Traversal (CWE-22) vulnerability in Std42 Elfinder. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 22% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2023-35840 is a path traversal vulnerability (CWE-22) in the _joinPath function within elFinderVolumeLocalFileSystem.class.php of the PHP LocalVolumeDriver connector. It affects elFinder versions prior to 2.1.62 and carries a CVSS 3.1 base score of 6.5.

An attacker with low-privileged network access and no user interaction required can exploit the flaw to perform unauthorized file modifications on the server, resulting in high integrity impact without affecting confidentiality or availability.

The referenced GitHub security advisory and the commit bb9aaa7b096a1b83f2f85657c43f12131ece2891 indicate that the issue is resolved by upgrading to elFinder 2.1.62 or later; public proof-of-concept repositories further document the path traversal vector in the LocalVolumeDriver.

EPSS remains flat at 0.0626 with no material increase after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

_joinPath in elFinderVolumeLocalFileSystem.class.php in elFinder before 2.1.62 allows path traversal in the PHP LocalVolumeDriver connector.

CWE(s)

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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2022-26960Same product: Std42 Elfinder
CVE-2021-32682Same product: Std42 Elfinder
CVE-2025-21048Shared CWE-22
CVE-2026-23939Shared CWE-22
CVE-2024-7145Shared CWE-22
CVE-2023-42225Shared CWE-22
CVE-2024-33109Shared CWE-22
CVE-2023-35016Shared CWE-22
CVE-2025-10723Shared CWE-22
CVE-2023-1163Shared CWE-22

Affected Assets

std42
elfinder
≤ 2.1.62

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

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-22

Validates pathnames and filenames to prevent traversal outside intended directories.

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.

finds

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

prevents

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

prevents

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

prevents

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

prevents

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

mitigates

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

References