Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2025-59049 is a high-severity Path Traversal (CWE-22) vulnerability. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 24% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
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.
Mockoon is an open-source tool for designing and running mock APIs. Prior to version 9.2.0, its static file serving feature generated server filenames through templating driven by user-supplied input, exposing the implementation to path traversal and local file inclusion. The affected code paths reside in the commons-server package, allowing an unauthenticated remote attacker to reference arbitrary files on the mock server filesystem. The flaw carries a CVSS 3.1 score of 7.5 and is tracked under CWE-22, CWE-24, and CWE-73; it is especially relevant for cloud-hosted deployments.
An attacker can supply crafted template values in a mock API route configuration to traverse directories and retrieve any readable file from the underlying host. Because the vulnerability is exploitable over the network without authentication or user interaction, an adversary could obtain configuration secrets, source code, or other sensitive data stored on the server.
The project’s security advisory GHSA-w7f9-wqc4-3wxr and the fixing commit c7f6e23e87dc3b8cc44e5802af046200a797bd2e indicate that the issue is resolved in Mockoon 9.2.0. The patch updates filename handling to prevent traversal sequences originating from user-controlled template input.
EPSS for the CVE rose from a low baseline to a peak of 0.0622 on 2025-12-11 before receding to the current value of 0.0191, indicating a measurable increase in exploitation interest several months after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-27607
Vulnerability Data
Mockoon provides way to design and run mock APIs. Prior to version 9.2.0, a mock API configuration for static file serving follows the same approach presented in the documentation page, where the server filename is generated via templating features from…
more
user input is vulnerable to Path Traversal and LFI, allowing an attacker to get any file in the mock server filesystem. The issue may be particularly relevant in cloud hosted server instances. Version 9.2.0 fixes the issue.
- 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 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.
Secure SDLC practices include input validation and path sanitization that eliminate this weakness.
Least-privilege file authorization directly limits damage from externally controlled paths.
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.
Secure coding standards require neutralizing ../ sequences and canonicalizing paths before file operations.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Information access restriction limits which files an application may read or write.