Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-44635 is a high-severity Path Traversal (CWE-22) vulnerability in Apache Fineract. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 0.7% 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 SI-2 (Flaw Remediation) — 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.
Apache Fineract versions 1.8.0 and earlier are affected by a path traversal vulnerability in the file upload component, tracked as CVE-2022-44635 and assigned CWE-22. The flaw permits an authenticated user to perform remote code execution on the server, carrying a CVSS 3.1 score of 8.8 that reflects network-accessible attack vector, low complexity, and full impact on confidentiality, integrity, and availability.
An attacker who already possesses valid credentials can exploit the issue to upload crafted files that traverse directories and execute arbitrary code, thereby gaining control over the affected Fineract instance.
Public advisories from the Apache project direct users to upgrade to version 1.8.1 as the primary mitigation, with corresponding notices published on the project mailing lists and Openwall.
The EPSS probability rose from lower values to a peak of 0.4096 on 2025-12-11 before receding to the current 0.1297, indicating that exploitation interest emerged after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-47571
Vulnerability Data
Apache Fineract allowed an authenticated user to perform remote code execution due to a path traversal vulnerability in a file upload component of Apache Fineract, allowing an attacker to run remote code. This issue affects Apache Fineract version 1.8.0 and…
more
prior versions. We recommend users to upgrade to 1.8.1.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Enforces validation of file paths and names during upload to block the path traversal that enables arbitrary code execution.
Requires prompt application of the vendor patch (upgrade to 1.8.1) that eliminates the path-traversal flaw in the file-upload component.
Deploys malicious-code detection mechanisms that can inspect uploaded files and block or alert on attempts to introduce executable payloads.
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.
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.
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.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.