CVE-2025-56132
Auth Bypass in Liquidfiles ≤ 4.2.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-56132 is a high-severity Authentication Bypass by Primary Weakness (CWE-305) vulnerability in Liquidfiles Liquidfiles. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-8 (Identification and Authentication (Non-organizational Users)) — 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.
LiquidFiles filetransfer server contains a user enumeration vulnerability in its password reset functionality, where the application returns distinguishable responses for valid versus invalid email addresses. This affects all versions prior to 4.2, which rely solely on basic IP-based rate limiting, while version 4.2 adds user-based lockout mechanisms that are not enabled by default. The issue is tracked as CWE-305 with a CVSS 3.1 score of 7.3.
Unauthenticated attackers can exploit the flaw by submitting password reset requests and observing response differences to confirm the existence of registered accounts. The IP-based controls present before version 4.2 can be bypassed through request distribution across multiple IPs or proxies, enabling enumeration that facilitates follow-on attacks such as password spraying.
Release notes for version 4.2 document the addition of user-level lockout protections, though enumeration remains possible under default settings. The EPSS score rose from a low baseline to a peak of 0.0783 on 2026-02-03 before receding to the current value of 0.0241, indicating a period of increased exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-31771
Vulnerability Data
LiquidFiles filetransfer server is vulnerable to a user enumeration issue in its password reset functionality. The application returns distinguishable responses for valid and invalid email addresses, allowing unauthenticated attackers to determine the existence of user accounts. Version 4.2 introduces user-based…
more
lockout mechanisms to mitigate brute-force attacks, user enumeration remains possible by default. In versions prior to 4.2, no such user-level protection is in place, only basic IP-based rate limiting is enforced. This IP-based protection can be bypassed by distributing requests across multiple IPs (e.g., rotating IP or proxies). Effectively bypassing both login and password reset security controls. Successful exploitation allows an attacker to enumerate valid email addresses registered for the application, increasing the risk of follow-up attacks such as password spraying.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 3 OS baselines
V6.4.3V7.2.4
Mitigating Controls (NIST 800-53 r5) AI
Requires unique identification and authentication of users, structurally blocking bypass of the mechanism.
Requires unique identification and authentication of non-organizational users, blocking bypass paths.
Enforces approved authorizations so a bypass weakness cannot be exploited to reach 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 development practices throughout the SDLC prevent the primary weaknesses that enable authentication bypass.
Strong authentication mechanisms and policy enforcement directly reduce bypass opportunities arising from implementation flaws.
Identifying and recording vulnerabilities catches the primary weaknesses that allow authentication bypass.
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 can detect authentication bypass conditions before deployment.
Secure development lifecycle reduces likelihood of introducing bypass flaws during implementation.
Secure coding practices help prevent the primary weakness that enables authentication bypass.
Information access restriction complements authentication by limiting what can be reached even if bypass occurs.
Secure authentication mechanisms directly address bypass risks in the implemented authentication process.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Ubuntu 22.04 (1 rule)
- V-260470 Ubuntu 22.04 LTS, when booted, must require authentication upon booting into single-user and maintenance modes. prevents CWE-305
Ubuntu 24.04 (1 rule)
- V-270675 Ubuntu 24.04 LTS when booted must require authentication upon booting into single-user and maintenance modes. prevents CWE-305