Cyber Resilience

CVE-2025-0632

Path Traversal

Published
21 April 2025
Modified
17 June 2026
CVSS Score v4 9.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:H/SI:L/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.0086 55th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2025-0632 is a critical-severity Path Traversal (CWE-22) vulnerability in Formulatrix Rock Maker (inferred from references). Its CVSS base score is 9.2 (Critical).

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.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — 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-0632 is a local file inclusion vulnerability in the Render function of Formulatrix Rock Maker Web that stems from improper handling of file paths, enabling remote attackers to read arbitrary files on the host. The flaw affects Rock Maker Web versions 3.2.1.1 and later and is tracked under CWE-22 and CWE-98, carrying a CVSS 4.0 score of 9.2.

An unauthenticated remote attacker can supply crafted input to the Render function to execute malicious scripts that automatically retrieve configuration files from known locations, exfiltrating credentials and other sensitive data. Because the application lacks rate limiting, the same vector also permits systematic enumeration of the host filesystem, which can escalate to full system compromise.

The vendor has published a security bulletin and an updated installer (RockMakerWeb_3.18.4.7_setup.exe) on its download portal that address the issue; administrators should apply the patched build and review the accompanying bulletin for configuration guidance.

EPSS for the CVE reached a peak of 0.0269 after disclosure before settling at the current value of 0.0154, indicating a measurable increase in exploitation interest following public release.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Local File Inclusion (LFI) vulnerability in a Render function of Formulatrix Rock Maker Web (RMW) allows a remote attacker to obtain sensitive data via arbitrary code execution. A malicious actor could execute malicious scripts to automatically download configuration files in…

more

known locations to exfiltrate data including credentials, and with no rate limiting a malicious actor could enumerate the filesystem of the host machine and potentially lead to full host compromise. This issue affects Rock Maker Web: from 3.2.1.1 and later

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-2025-52562Shared CWE-22, CWE-98
CVE-2026-48820Shared CWE-22, CWE-98
CVE-2026-44177Shared CWE-22, CWE-98
CVE-2023-6989Shared CWE-22, CWE-98
CVE-2026-33513Shared CWE-22, CWE-98
CVE-2025-60574Shared CWE-22, CWE-98
CVE-2023-6583Shared CWE-22, CWE-98
CVE-2026-1988Shared CWE-98
CVE-2025-21048Shared CWE-22
CVE-2024-7145Shared CWE-22

Affected Assets

Formulatrix
Rock Maker
inferred from references and description; NVD did not file a CPE for this CVE

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.

Developer testing and static analysis can discover missing filename restrictions before deployment.

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

Information-flow rules can block the loading of external or unauthorized files into the PHP process.

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 such as input validation and allow-listing of include paths directly prevent the weakness.

PR.PS-01 partial match
prevents

Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.

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.

PR.PS-05 partial match
prevents

Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.

PR.AA-05 none match
prevents

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.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

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

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References