Authenticator LoginDrupal extension · Authenticator Login Project
CVE-2025-31681
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 · uneditedMissing Authorization vulnerability in Drupal Authenticator Login allows Forceful Browsing.This issue affects Authenticator Login: from 0.0.0 before 2.0.6.
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 confidenceMissing authorization vulnerability in Drupal Authenticator Login module allows forceful browsing, enabling unauthorized users to access protected resources by directly navigating to restricted URLs without proper authentication checks.
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
Authenticator LoginDrupal extension
< 2.0.6CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Locate Authenticator Login module installationCheck your Drupal installation's modules directory for the authenticator_login folder, typically at /modules/contrib/authenticator_login/ or /web/modules/contrib/authenticator_login/Affected if The authenticator_login folder exists in your modules directory
-
Identify installed module versionOpen the authenticator_login.info.yml file inside the module directory and read the 'version:' field, or check the composer.json file for the 'version' entry under 'extra.drupal' or the installed version in your composer.lockAffected if The version listed is below 2.0.6 (for example: 2.0.5, 2.0.4, or any version starting with 2.0.x where x is less than 6)
-
Verify module is enabledRun drush pm-list --status=enabled | grep authenticator_login or check the Drupal admin interface at /admin/modules to confirm the Authenticator Login module is enabledAffected if The module shows as enabled in Drupal's module list
If the Authenticator Login module is installed and enabled with a version lower than 2.0.6, your environment is affected by this authorization bypass vulnerability.
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 · scoped2.0.6
Upgrade to Authenticator Login version 2.0.6 or later which includes proper authorization controls; if unable to upgrade immediately, audit all protected routes and implement access checks on authentication-related endpoints.
2.0.6
- 1. Back up your Drupal site database and files before making any changes.
- 2. Update the Authenticator Login module to version 2.0.6 using your preferred method (Drush, Composer, or Drupal admin interface).
- 3. Clear Drupal caches after the update to ensure the new module code is loaded.
- 4. Verify the update was successful by checking the module version in the Drupal admin interface or via Drush: drush pm-list | grep authenticator_login.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Authenticator Login
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31681 — 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-31681 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