Cyber Resilience

CVE-2024-7458

Path Traversal in Eladmin ≤ 2.7

Public PoCPath Traversal
Published
04 August 2024
Modified
06 August 2024
Patch / advisory
CVSS Score v4 5.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0084 55th percentile
Risk Priority 30 floored blend · peak EPSS

Summary

CVE-2024-7458 is a medium-severity Path Traversal: 'dir/../../filename' (CWE-27) vulnerability in Eladmin Eladmin. Its CVSS base score is 5.1 (Medium).

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

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)

EU & UK References

Vulnerability Data

A vulnerability was found in elunez eladmin up to 2.7 and classified as critical. This issue affects some unknown processing of the file /api/deploy/upload /api/database/upload of the component Database Management/Deployment Management. The manipulation of the argument file leads to path…

more

traversal: 'dir/../../filename'. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-273551.

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-2024-51747Shared CWE-22, CWE-27
CVE-2023-20129Shared CWE-22, CWE-27
CVE-2026-62391Shared CWE-22, CWE-27
CVE-2024-27764Shared CWE-22, CWE-27
CVE-2025-66518Shared CWE-22, CWE-27
CVE-2024-23897Shared CWE-22, CWE-27
CVE-2023-50254Shared CWE-22, CWE-27
CVE-2023-34125Shared CWE-22, CWE-27
CVE-2023-27588Shared CWE-22, CWE-27
CVE-2024-20348Shared CWE-22, CWE-27

Affected Assets

eladmin
eladmin
≤ 2.7

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

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

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

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

Secure SDLC practices directly require input validation and path sanitization that prevent directory traversal flaws.

ID.RA-01 partial match
prevents

Vulnerability identification processes will discover path traversal weaknesses during code or configuration review.

PR.AA-05 partial match
prevents

Least-privilege file permissions and access enforcement can limit the damage from a successful traversal.

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.

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.

prevents

Secure coding standards require neutralizing '../' sequences and using safe file APIs, eliminating this exact weakness.

finds

Security testing in development catches path-traversal flaws before release but does not itself implement the control.

prevents

Secure development lifecycle mandates input validation and path sanitization that directly prevents directory traversal.

prevents

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

prevents

Secure architecture principles discourage unsafe path construction but do not prescribe the specific coding fix.

mitigates

Information access restriction can limit which files are reachable, reducing impact but not preventing the traversal vector.

References