dbcve.org
Miniorange 2faDrupal extension · Miniorange

CVE-2025-47709

MEDIUM · 6.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 →
74/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in Drupal Enterprise MFA - TFA for Drupal allows Forceful Browsing.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

Missing Authorization vulnerability in Drupal Enterprise MFA - TFA module allows Forceful Browsing, where authenticated users can bypass intended access controls and access MFA-protected resources or functionality they should not have access to by directly navigating to restricted URLs or endpoints.

MitigationUpgrade to version 4.7.0 or later (for 4.x branch) or 5.2.0 or later (for 5.x branch) to resolve the authorization bypass. Verify MFA functionality works correctly after the upgrade.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 if Miniorange TFA module is installed
    Run 'drush pm-list' or check the Drupal modules directory for the miniorange_tfa or tfa module. Look for modules named 'miniorange_2fa', 'tfa', or 'miniorange_tfa' in the /modules directory.
    Affected if The Miniorange TFA module is present in the Drupal installation.
  2. Determine the installed module version
    Run 'drush pm-info miniorange_2fa' or check the module's .info.yml file for the version number. Compare against affected ranges: 5.0.0 <= version < 5.2.0 OR 7.x-2.16 <= version < 8.x-4.7.
    Affected if The installed version falls within the affected ranges.
  3. Verify MFA functionality is enabled
    Check the Drupal configuration at /admin/config/people/tfa or run 'drush config-get tfa.settings' to see if TFA/MFA is actually enabled for the site.
    Affected if TFA/MFA is enabled and configured for user authentication.
  4. Check for custom access restrictions on sensitive endpoints
    Review Drupal permissions and menu router entries for paths like /user/*/security, /admin/config/people/tfa, or any custom MFA-protected routes. Verify these paths have appropriate role-based access controls defined.
    Affected if Sensitive endpoints lack proper role-based access controls and are accessible to authenticated users who should not have access.

A user is affected if the Miniorange TFA module versions 5.0.0 to <5.2.0 or 7.x-2.16 to <8.x-4.7 are installed with MFA enabled, allowing authenticated users to bypass authorization via direct URL access to protected resources.

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 to version 4.7.0 or later (for 4.x branch) or 5.2.0 or later (for 5.x branch) to resolve the authorization bypass. Verify MFA functionality works correctly after the upgrade.

Recommended fix High confidence

Upgrade to miniOrange 2FA version 5.2.0 (for 5.x branch) or 8.x-4.7/4.7.0 (for older branches)

  1. 1. Identify the currently installed miniOrange 2FA module version in your Drupal environment
  2. 2. If using version 5.x (5.0.0 to 5.1.x), upgrade to version 5.2.0 or later
  3. 3. If using version 7.x-2.16 through 7.x-2.x or 8.x versions before 8.x-4.7, upgrade to version 8.x-4.7 or later
  4. 4. If using versions before 4.7.0 in the 4.x line, upgrade to version 4.7.0 or later
  5. 5. Clear Drupal cache after upgrading: drush cr
  6. 6. Verify the module is functioning correctly and test the 2FA flow
  7. 7. Review user roles and permissions to ensure proper authorization controls are in place
Caveat Review module release notes for any configuration or feature changes between versions; test in staging environment before production deployment

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

Fix this in Miniorange 2fa Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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