dbcve.org
Miniorange 2faDrupal extension · Miniorange

CVE-2025-47707

HIGH · 7.5 CVSS v3.1 Published 2025-05-14
Fix available
A fix is available. Upgrade to 5.2.0 / 8.x-4.7 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
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.7.0, from 5.0.0 before 5.2.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 · high confidence

Authentication bypass vulnerability in the Enterprise MFA - TFA for Drupal module allows attackers to circumvent the two-factor authentication mechanism, potentially gaining unauthorized access to user accounts that should require MFA verification.

MitigationUpgrade Enterprise MFA - TFA for Drupal to version 4.7.0 or later (for 4.x branch) or 5.2.0 or later (for 5.x branch) to apply the security patch.

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
Miniorange 2faDrupal extension
Affected:>= 5.0.0, < 5.2.0>= 7.x-2.16, < 8.x-4.7

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Identify MiniOrange 2FA module version
    Locate the miniorange_2fa module in your Drupal installation (typically in modules/contrib/miniorange_2fa or similar) and check the info.yml or module version file. Alternatively, use Drush command: drush pm-list --type=module --status=enabled | grep miniorange
    Affected if The installed version is 5.0.0 to 5.1.x (for 5.x branch) OR 7.x-2.16 to 8.x-4.6 (for 8.x branch)
  2. Confirm the module is enabled
    Check if the miniorange_2fa module is in enabled status via Drupal admin interface at Extend page or using: drush pm-list --status=enabled --type=module
    Affected if The module appears in the enabled module list
  3. Verify TFA/MFA is configured for user accounts
    Navigate to Configuration > People > Two-factor authentication (or similar path in your Drupal admin) and check if any TFA policies are enabled. Also check if users have TFA trusted devices or backup codes configured.
    Affected if TFA is enabled and enforced for user accounts in your Drupal site
  4. Check authentication methods in use
    Review the authentication methods enabled in the MiniOrange 2FA settings: look at the configured second factor methods (e.g., QR code, email OTP, soft token, push notification) in the module configuration page.
    Affected if Any second-factor authentication methods are actively configured for use

You are affected if the MiniOrange 2FA module version is 5.0.0 through 5.1.x (5.x branch) or 7.x-2.16 through 8.x-4.6 (8.x branch) AND TFA is enabled for user accounts on your Drupal site.

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 5.2.0 / 8.x-4.7 or later
Fixed in 5.2.08.x-4.7
Interim mitigation

Upgrade Enterprise MFA - TFA for Drupal to version 4.7.0 or later (for 4.x branch) or 5.2.0 or later (for 5.x branch) to apply the security patch.

Recommended fix High confidence

4.7.0 or 5.2.0 (or later respective branch)

  1. 1. Identify the currently installed version of the miniorange 2fa module in your Drupal installation
  2. 2. If using version 5.0.0 through 5.1.x, upgrade to version 5.2.0 or later
  3. 3. If using version 7.x-2.16 through 8.x-4.6, upgrade to version 8.x-4.7 or later
  4. 4. If using version 0.0.0 or any version before 4.7.0, upgrade to version 4.7.0 or later
  5. 5. Clear Drupal cache after upgrading the module
  6. 6. Verify that two-factor authentication is functioning correctly after the upgrade
Caveat Review module release notes for any configuration or API changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Miniorange 2fa Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47707 — 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-47707 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