Skip to main content
VulnerabilityPublished Updated

CVE-2025-7393: Mail login · This module enables users to login by email address with the minimal configurations

Affects drupal/mail_loginSource GCVE Database

0
Compare
Authoritative record:CVE-2025-7393· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical : upgrade to 4.2.0 or 3.2.0 as a priority.

Data as of 15 Nov 2026, 01:53 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.2.0, 3.2.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Upgrade drupal/mail_login to 4.2.0 or 3.2.0.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/mail_loginAffected
  • <3.2.0
  • >=4.0.0 <4.2.0
Fixed in
  • 3.2.0
  • 4.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official fixes by upgrading to mail_login module versions 3.2.0 or 4.2.0 or later. These versions contain the necessary patches to fully address the brute force protection bypass vulnerability.

Description

The Drupal mail_login module allows users to log in using their email address with minimal configuration. It contains incomplete brute force protection on the login form, which an attacker could bypass to potentially gain unauthorized account access. Fixed versions 3.2.0 and 4.2.0 address this issue.

References

Community reviews

Loading reviews…