CVE-2025-68916
Path Traversal in Riello-Ups Netman 208 ≤ 1.12
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-68916 is a critical-severity Path Traversal: '/../filedir' (CWE-25) vulnerability in Riello-Ups Netman 208. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 18% 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.
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-68916 is a directory traversal vulnerability affecting the Riello UPS NetMan 208 Application in versions before 1.12. The issue resides in the cgi-bin/certsupload.cgi endpoint, which permits path traversal via /../ sequences during file uploads, enabling arbitrary file placement and resultant remote code execution. It is classified under CWE-25 (Path Traversal: '.../...') and CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), with a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).
The vulnerability can be exploited by a privileged user (PR:H) over the network (AV:N) with low attack complexity (AC:L) and no user interaction (UI:N). Successful exploitation allows the attacker to upload malicious files to arbitrary locations, leading to code execution on the target system. This results in high impacts to confidentiality, integrity, and availability (C:H/I:H/A:H), compounded by a change in scope (S:C) that amplifies the attack surface.
Mitigation details are available in the advisory published at https://github.com/gerico-lab/riello-multiple-vulnerabilities-2025, which covers this and related Riello vulnerabilities.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-205298
Vulnerability Data
Riello UPS NetMan 208 Application before 1.12 allows cgi-bin/certsupload.cgi /../ directory traversal for file upload with resultant code execution.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
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 path traversal sequences such as '/../' in externally supplied filenames before they are used to construct paths.
Information flow enforcement can block unauthorized data flows that would result from a successful path traversal.
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.
Secure SDLC practices directly require input validation and path sanitization that prevent traversal flaws.
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 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.
Secure coding standards require canonicalization and neutralization of '../' sequences in path construction.
Security testing in development catches path-traversal flaws before production deployment.
Secure development lifecycle mandates input validation and path sanitization that directly prevents traversal sequences.
Application security requirements explicitly call for controls against path traversal and directory escape attacks.
Secure architecture principles reduce exposure to path traversal through least-privilege file-system design.
Information access restriction limits which directories users or processes may traverse.