Vulnerability from drupal
Published
2025-11-05 18:08
Modified
2025-11-05 18:08
Summary
Details

The Email TFA module provides additional email-based two-factor authentication for Drupal logins.

In certain scenarios, the module does not fully protect all login mechanisms as expected.

This issue is mitigated by the fact that an attacker must already have valid user credentials (username and password) to take advantage of the weakness.

Credits
Pierre Rudloff (prudloff) www.drupal.org/u/prudloff
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "affected_versions": "\u003c2.0.6"
      },
      "package": {
        "ecosystem": "Packagist:https://packages.drupal.org/8",
        "name": "drupal/email_tfa"
      },
      "ranges": [
        {
          "database_specific": {
            "constraint": "\u003c2.0.6"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "severity": []
    }
  ],
  "aliases": [
    "CVE-2025-12760"
  ],
  "credits": [
    {
      "contact": [
        "https://www.drupal.org/u/prudloff"
      ],
      "name": "Pierre Rudloff (prudloff)"
    }
  ],
  "details": "The Email TFA module provides additional email-based two-factor authentication for Drupal logins.\n\nIn certain scenarios, the module does not fully protect all login mechanisms as expected.\n\nThis issue is mitigated by the fact that an attacker must already have valid user credentials (username and password) to take advantage of the weakness.",
  "id": "DRUPAL-CONTRIB-2025-115",
  "modified": "2025-11-05T18:08:01.000Z",
  "published": "2025-11-05T18:08:01.000Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.drupal.org/sa-contrib-2025-115"
    }
  ],
  "schema_version": "1.7.0"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.