CVE-2026-57490
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-57490 is a high-severity Use of Single-factor Authentication (CWE-308) vulnerability. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Remote Services (T1021); ranked at the 34th 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.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-101637
Vulnerability Data
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.16.0, when an administrator has enabled WebDAV, FileRise WebDAV Basic authentication validates only the account username and password through AuthModel::authenticate() and does not enforce…
more
the account's configured TOTP factor. An attacker who knows valid primary credentials for a TOTP-enabled account can authenticate to the enabled WebDAV service without supplying the second factor and exercise the account's WebDAV file permissions. The browser login path enforces TOTP, but the separate public/webdav.php authentication callback did not. This issue is fixed in version 3.16.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.3.4V6.3.6V6.4.2V6.4.3
Mitigating Controls (NIST 800-53 r5) AI
ia-2 requires unique identification and authentication of users, directly stopping single-factor schemes by mandating appropriate (multi-factor) mechanisms.
ia-8 requires unique identification and authentication of non-organizational users, directly stopping single-factor schemes by mandating appropriate (multi-factor) mechanisms.
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.
Explicit MFA requirement directly eliminates single-factor authentication while the control also addresses broader authentication scope.
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.
A.5.15 only requires defining and documenting an access control policy plus requirements (including references to other controls); it performs no authentication enforcement or multi-factor mandate that would stop single-factor authentication from being exploitable.
Authentication information control directly addresses the need for strong, multi-factor credentials.
Access rights provisioning can require MFA, yet the control is broader than authentication strength.
Privileged access rights can be conditioned on MFA, but the control focuses on privilege scope rather than factor count.