Skip to main content
CVE-2025-6675VulnerabilityPublished Updated

CVE-2025-6675: Enterprise MFA – TFA for Drupal · Authentication Bypass Using an Alternate Path or Channel

Affects Enterprise MFA – TFA for DrupalSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Drupal Enterprise MFA - TFA for DrupalAffected
  • =0.0.0
  • =5.2.0
Fixed in–

AI-suggested

To mitigate CVE-2025-6675, organizations should: 1) Monitor Drupal security advisories and promptly apply patches or updates to the Enterprise MFA - TFA module as soon as they are released, specifically upgrading to versions 4.8.0 or later, 5.2.1 or later, or the latest stable releases beyond 5.1.*. 2) Implement additional access controls such as IP whitelisting, VPN requirements, or network segmentation to limit exposure of authentication endpoints. 3) Employ comprehensive logging and monitoring to detect suspicious login attempts or anomalies indicative of bypass attempts. 4) Conduct regular security assessments and penetration testing focused on authentication mechanisms to identify potential weaknesses. 5) Consider deploying layered authentication strategies, including hardware tokens or biometric factors, to reduce reliance on a single MFA module. 6) Educate administrators and users about the risks and signs of compromised accounts. 7) Temporarily disable or restrict the use of the vulnerable MFA module if immediate patching is not feasible, while implementing compensating controls to maintain security.

Description

Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Enterprise MFA - TFA for Drupal allows Authentication Bypass.This issue affects Enterprise MFA - TFA for Drupal: from 0.0.0 before 4.8.0, from 5.2.0 before 5.2.1, from 0.0.0 before 5.0.*, from 0.0.0 before 5.1.*.

References

Community reviews

Loading reviews…