# CVE-2025-7393: Mail Login - Critical - Access bypass - SA-CONTRIB-2025-088

> Attackers can bypass authentication restrictions to perform brute force attacks on user accounts in the Drupal Mail Login module.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** DRUPAL-CONTRIB-2025-088, GHSA-jf2c-8v4p-mgg2

## What is CVE-2025-7393?

CVE-2025-7393 is a critical authentication bypass vulnerability in Drupal Mail Login, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Restriction of Excessive Authentication Attempts vulnerability in Drupal Mail Login allows Brute Force.This issue affects Mail Login: from 3.0.0 before 3.2.0, from 4.0.0 before 4.2.0.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2025-7393?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/mail_login` | Packagist:https://packages.drupal.org/8 | All versions | 3.2.0, 4.2.0 |

Products: Mqanneh Mail Login.

## How do I fix CVE-2025-7393?

Upgrade to a fixed version.

## Is CVE-2025-7393 being exploited?

There is no known exploitation of CVE-2025-7393 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7393 and fix it if it is affected.

What it is: CVE-2025-7393 is a critical authentication bypass vulnerability in Drupal Mail Login, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7393 in the wild and no public exploit code.

Affected product: Drupal Mail Login. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7393/ (Markdown: https://insights.sbomify.com/CVE-2025-7393/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7393
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7393
- OSV: https://osv.dev/vulnerability/CVE-2025-7393

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7393/
Summaries are generated and may contain mistakes; the official description above is the record.