dbcve.org
Two Factor AuthenticationDrupal extension · Two Factor Authentication Project

CVE-2025-7030

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 8.x-1.11 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Privilege Defined With Unsafe Actions vulnerability in Drupal Two-factor Authentication (TFA) allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Two-factor Authentication (TFA): from 0.0.0 before 1.11.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 confidence

This is a privilege escalation vulnerability in Drupal's Two-factor Authentication (TFA) module. The 'Privilege Defined With Unsafe Actions' flaw allows authenticated users to exploit incorrectly configured access control security levels, potentially bypassing 2FA protections or accessing unauthorized functions. The vulnerability exists in all versions before 1.11.0.

MitigationUpdate the Two-factor Authentication (TFA) module to version 1.11.0 or later to resolve the improper access control configuration.

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
Affected:< 8.x-1.11

CVSS 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
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the TFA module is installed
    Run 'drush pm-list' or check the Drupal admin UI at /admin/modules to confirm the Two Factor Authentication module is present in the codebase.
    Affected if The Two Factor Authentication module is found in the Drupal installation.
  2. Determine the installed TFA module version
    Run 'drush pm:list --field=name=two_factor_authentication' or check the module's .info.yml file in modules/two_factor_authentication to read the version number.
    Affected if The installed version is below 8.x-1.11 (for example, 8.x-1.10, 8.x-1.9, etc.).
  3. Check if TFA module is enabled
    Run 'drush state:get module.two_factor_authentication' or check the Drupal admin UI at /admin/modules to see if the module is enabled.
    Affected if The TFA module is enabled and active in the Drupal installation.
  4. Verify TFA is configured for user roles
    Navigate to /admin/config/people/tfa or run 'drush config:export' to inspect the TFA role configuration settings.
    Affected if TFA is enabled and assigned to any user roles, making the privilege escalation flaw applicable.
  5. Inspect access control configuration for TFA
    Review the TFA module configuration at /admin/config/people/tfa/settings or export the configuration to check for any custom or incorrectly defined access rules.
    Affected if There are custom access control rules or unsafe action definitions configured in the TFA module settings.

The environment is affected if the Two Factor Authentication module is installed, enabled, running a version below 8.x-1.11, and has TFA protections or role-based access controls configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.x-1.11 or later
Fixed in 8.x-1.11
Interim mitigation

Update the Two-factor Authentication (TFA) module to version 1.11.0 or later to resolve the improper access control configuration.

Recommended fix High confidence

8.x-1.11.0 or later

  1. Backup your Drupal site database and files
  2. Update the Two Factor Authentication (TFA) module to version 1.11.0 or later using Composer (composer update drupal/tfa) or Drupal's web interface
  3. Run database updates if any are required (drush updatedb or via admin UI)
  4. Clear Drupal caches (drush cr)
  5. Verify the TFA module shows version 1.11.0 or later on the Extend page
  6. Test that two-factor authentication still functions correctly for affected users

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7030 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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