Two Factor AuthenticationDrupal extension · Two Factor Authentication Project
CVE-2025-31694
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect Authorization vulnerability in Drupal Two-factor Authentication (TFA) allows Forceful Browsing.This issue affects Two-factor Authentication (TFA): from 0.0.0 before 1.10.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn incorrect authorization vulnerability in Drupal's Two-factor Authentication (TFA) module allows forceful browsing, enabling attackers to potentially bypass 2FA enforcement and access protected resources without completing the required second authentication factor.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Two Factor AuthenticationDrupal extension
< 8.x-1.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify TFA module is installedRun 'drush pm-list --status=enabled' or check Drupal's module directory for the tfa module presenceAffected if The tfa module appears in the list of enabled modules
-
Check installed TFA module versionRun 'drush pm:security' or inspect the tfa.info.yml file in the module directory for the version numberAffected if The version is below 8.x-1.10 (e.g., 8.x-1.9, 8.x-1.8, etc.)
-
Confirm TFA is actually enforced on the siteNavigate to People > Permissions > Two-factor Authentication settings, or check user roles for 'require TFA' configurationAffected if TFA is enabled and required for user accounts or specific roles
-
Check for exposed TFA validation endpointsReview site configuration and routing for /tfa/validate or similar endpoints accessible without authenticationAffected if TFA validation endpoints are accessible to anonymous users or unauthenticated requests
The site is affected if the TFA module version is below 8.x-1.10 AND TFA is enabled and enforced for user accounts, allowing potential bypass of the second authentication factor.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.x-1.10
Update the Drupal TFA module to version 1.10.0 or later to remediate this authorization bypass vulnerability.
8.x-1.10.0
- Back up your Drupal site database and codebase before making changes
- Run `composer require drupal/tfa:^1.10` to update the Two Factor Authentication module to version 1.10.0 or later
- Run database updates using `drush updatedb` or via the Drupal administration UI at /update.php
- Clear the Drupal cache using `drush cr` or via the administration UI
- Verify the TFA module is now running version 1.10.0 or higher at admin/modules
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Two Factor Authentication
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31694 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data