# CVE-2025-31676: Email TFA - Moderately critical - Access bypass - SA-CONTRIB-2025-001

> Attackers can bypass two-factor authentication via brute force attacks, potentially taking over user accounts.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Mar 2025
- **Updated:** 19 Jun 2025
- **Also known as:** DRUPAL-CONTRIB-2025-001, GHSA-34w4-3qr3-m637

## What is CVE-2025-31676?

CVE-2025-31676 is a high-severity authentication bypass vulnerability in Drupal Email TFA, published on 31 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Weak Authentication vulnerability in Drupal Email TFA allows Brute Force.This issue affects Email TFA: from 0.0.0 before 2.0.3.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/email_tfa` | Packagist:https://packages.drupal.org/8 | From 2.0.0 | 2.0.3 |

Products: Email Tfa Project Email Tfa.

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

Upgrade to a fixed version.

## Is CVE-2025-31676 being exploited?

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

## Other vulnerabilities in Drupal Email TFA

- [CVE-2025-12760](https://insights.sbomify.com/CVE-2025-12760/): Email TFA - Moderately critical - Access bypass - SA-CONTRIB-2025-115 (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31676 is a high-severity authentication bypass vulnerability in Drupal Email TFA, published on 31 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31676 in the wild and no public exploit code.

Affected product: Drupal Email TFA. 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-31676/ (Markdown: https://insights.sbomify.com/CVE-2025-31676/index.md)
```

## Sources

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

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