CVE-2025-54769
Xorux Lpar2Rrd ≤ 8.04
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-54769 is a high-severity Path Traversal: '../filedir' (CWE-24) vulnerability in Xorux Lpar2Rrd. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 14% 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 SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
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-2025-54769 is a path traversal vulnerability affecting an application that permits file uploads and relies on Perl modules. An authenticated read-only user can combine an upload with directory traversal to write an arbitrary file to any location on the server, including locations that overwrite existing Perl modules.
An attacker with read-only credentials can exploit the flaw over the network without user interaction to place a malicious module that the application subsequently loads, resulting in remote code execution with impacts on confidentiality, integrity, and availability. The CVSS 3.1 base score of 8.8 reflects the low attack complexity and the privilege escalation from read-only to full system control.
Public advisories referenced at korelogic.com, lpar2rrd.com, and seclists.org detail the issue and are the primary sources for patch or configuration guidance. The associated EPSS score has remained flat at 0.0934 with no material increase since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-22956
Vulnerability Data
An authenticated, read-only user can upload a file and perform a directory traversal to have the uploaded file placed in a location of their choosing. This can be used to overwrite existing PERL modules within the application to achieve remote…
more
code execution (RCE) by an attacker.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1V3.5.2V6.4.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover incorrect calls to privileged APIs before deployment.
Input validation directly neutralizes '../' sequences in externally-supplied pathnames before they are resolved.
Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.
Enforced access authorizations can limit the damage even when path traversal succeeds.
Least-privilege assignment directly reduces both the availability of privileged APIs and the blast radius when they are invoked incorrectly.
Least functionality restricts the file types and automatic processing capabilities the system will accept.
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.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Secure SDLC practices directly require input validation and path sanitization that prevent ../ traversal.
Hardened configuration baselines can enforce allowed file types and processing rules.
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.
Secure coding standards require neutralizing ../ sequences and canonicalizing paths before file operations.
Security testing in development catches path-traversal flaws before release.
Restricting privileged utility programs limits the exposure of privileged APIs to misuse.
Privileged access rights directly govern the correct use of privileged APIs and reduce misuse.
Secure SDLC mandates input validation and path canonicalization that directly block ../ traversal.
Application security requirements explicitly call for controls against path traversal in file-handling functions.