CVE-2025-31676
Email Tfa Project Email Tfa ≤ 2.0.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-31676 is a high-severity Weak Authentication (CWE-1390) vulnerability in Email Tfa Project Email Tfa. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 42th 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 AC-7 (Unsuccessful Logon Attempts) and IA-12 (Identity Proofing) — 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-31676 is a weak authentication vulnerability in the Drupal Email TFA module that allows brute force attacks. The issue affects Email TFA versions from 0.0.0 before 2.0.3 and is associated with CWEs-1390 (Weak Authentication) and CWE-307 (Improper Restriction of Excessive Authentication Attempts). It carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to network accessibility, low attack complexity, and significant impacts on confidentiality, integrity, and availability.
An attacker with low privileges, such as a registered Drupal user, can exploit this vulnerability remotely without user interaction. By brute-forcing the email-based two-factor authentication mechanism, the attacker can bypass weak protections, potentially achieving account takeover, unauthorized access to sensitive data, or further compromise of the Drupal site.
The Drupal security advisory SA-CONTRIB-2025-001 (https://www.drupal.org/sa-contrib-2025-001) details the vulnerability and recommends upgrading to Email TFA version 2.0.3 or later as the primary mitigation.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-9048
Vulnerability Data
Weak Authentication vulnerability in Drupal Email TFA allows Brute Force.This issue affects Email TFA: from 0.0.0 before 2.0.3.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 11 hardening rules · 7 OS baselines
V7.6.1V6.3.6V6.4.2V6.4.4
Mitigating Controls (NIST 800-53 r5) AI
AC-7 directly enforces limits on consecutive failed logons, structurally blocking brute-force exploitation of the weakness.
Requires identity proofing at appropriate assurance levels before granting accounts, directly addressing insufficient proof of identity.
Requires unique identification and authentication of users, directly stopping weak mechanisms from being used.
Requires device identification and authentication before establishing connections.
Extends strong identification and authentication requirements to non-organizational users.
Mandates proper authenticator issuance, management, and strength to ensure claimed identities are verified.
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.
Explicitly requires authentication of users/services/hardware with MFA and password-strength controls.
Identity proofing and binding is a core prerequisite for non-weak authentication.
Behavioral monitoring of authentication activity can detect excessive failed attempts after they occur.
Credential management directly supports stronger authentication but does not guarantee proof of identity.
Generating auth logs enables later detection or forensics but does not itself restrict attempts.
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.
Mandating multi-factor and non-password authentication techniques counters the use of inherently weak single-factor or password-only authentication mechanisms.
Strong-password and non-reuse requirements raise the bar against weak single-factor authentication that can be exploited via guessing or credential stuffing.
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).
Oracle Linux 8 (1 rule)
- V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-1390
RHEL 7 (3 rules)
- V-204427 The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe. prevents CWE-307
- V-204428 The Red Hat Enterprise Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period. prevents CWE-307
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-1390
RHEL 8 (1 rule)
- V-230492 RHEL 8 must not have the rsh-server package installed. prevents CWE-1390
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-1390
Windows 10 (1 rule)
- V-220865 The Windows Remote Management (WinRM) service must not use Basic authentication. prevents CWE-1390
Windows 11 (1 rule)
- V-253418 The Windows Remote Management (WinRM) service must not use Basic authentication. prevents CWE-1390