CVE-2025-41723
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-41723 is a critical-severity Path Traversal: '.../...//' (CWE-35) vulnerability in Certvde (inferred from references). Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 33% 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.
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-41723 is a directory traversal vulnerability in the importFile SOAP method, enabling an unauthenticated remote attacker to bypass path restrictions and upload files to arbitrary locations on the affected system. Published on 2025-10-22 with a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), it is associated with CWE-35 (Path Traversal).
An unauthenticated attacker with network access can exploit this vulnerability with low complexity and no user interaction required. Successful exploitation allows arbitrary file uploads, potentially leading to high confidentiality, integrity, and availability impacts, such as overwriting critical files or deploying malicious payloads.
For mitigation details, refer to the vendor advisory at https://sauter.csaf-tp.certvde.com/.well-known/csaf/white/2025/vde-2025-060.json.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-35335
Vulnerability Data
The importFile SOAP method is vulnerable to a directory traversal attack. An unauthenticated remote attacker bypass the path restriction and upload files to arbitrary locations.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
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.
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.
Security testing in development can detect path-traversal flaws before release.
Secure SDLC mandates input validation and path-handling controls that directly mitigate path traversal.
Application security requirements include rules for safe file-path construction and canonicalization.
Secure architecture principles require proper directory restrictions and input sanitization to prevent traversal.
Secure coding standards explicitly forbid unsafe path concatenation and mandate canonicalization routines.
Information access restriction limits file reachability but does not address the input-validation flaw itself.