Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-4320 is a critical-severity Authentication Bypass by Primary Weakness (CWE-305) vulnerability in Gov (inferred from references). Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 38th 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-12 (Identity Proofing) and IA-2 (Identification and Authentication (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.
CVE-2025-4320 is an Authentication Bypass by Primary Weakness vulnerability stemming from a weak password recovery mechanism for forgotten passwords in the Sufirmam software developed by Birebirsoft Software and Technology Solutions. This flaw enables authentication bypass and password recovery exploitation, affecting all versions of Sufirmam through 23012026. The vulnerability is associated with CWE-305 (Authentication Bypass by Primary Weakness) and CWE-640 (Weak Password Recovery Mechanism for Forgotten Password), and it has a CVSS v3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), indicating critical severity due to its network accessibility, low complexity, lack of required privileges or user interaction, and scope change with high impacts across confidentiality, integrity, and availability.
An unauthenticated attacker with network access can exploit this vulnerability remotely with low complexity and no user interaction required. Successful exploitation allows the attacker to bypass authentication mechanisms and perform password recovery operations, potentially gaining unauthorized access to the system and compromising sensitive data or administrative functions.
The primary reference is a notification from the Turkish National Cyber Incident Response Center (USOM) at https://www.usom.gov.tr/bildirim/tr-26-0005. The vendor was contacted early regarding this disclosure but did not respond, and no patches or specific mitigations are detailed in the available information. Security practitioners should isolate affected Sufirmam instances, monitor for anomalous authentication attempts, and consider disabling password recovery features until further vendor guidance is available.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-4414
Vulnerability Data
Authentication Bypass by Primary Weakness, Weak Password Recovery Mechanism for Forgotten Password vulnerability in Birebirsoft Software and Technology Solutions Sufirmam allows Authentication Bypass, Password Recovery Exploitation. This issue affects Sufirmam: through 23012026. NOTE: The vendor was contacted early about this…
more
disclosure but did not respond in any way.
- 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.4V7.4.3
Mitigating Controls (NIST 800-53 r5) AI
Identity proofing at appropriate assurance levels ensures forgotten-password recovery cannot succeed without strong verification of the user.
Requires unique identification and authentication of users, structurally blocking bypass of the mechanism.
Authenticator management requires secure distribution, reset, and verification procedures that directly address weak password recovery flows.
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.
Credential lifecycle management directly includes password reset/recovery flows.
Identity proofing is the core control that prevents weak or bypassed recovery mechanisms.
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.
Strong authentication-information lifecycle rules directly address weak password-recovery flows.
Secure development lifecycle reduces likelihood of introducing bypass flaws during implementation.
Application-security requirements can mandate secure recovery flows, but the control covers many other requirements.
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.
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