Two Factor AuthenticationDrupal extension · Two Factor Authentication Project
CVE-2024-13239
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 · uneditedWeak Authentication vulnerability in Drupal Two-factor Authentication (TFA) allows Authentication Abuse.This issue affects Two-factor Authentication (TFA): from 0.0.0 before 1.5.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 confidenceWeak authentication vulnerability in the Drupal Two-factor Authentication (TFA) module allows authentication abuse. The flaw exists in versions prior to 1.5.0, enabling attackers to bypass or circumvent the 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.5CVSS 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 the TFA module versionCheck the module's .info.yml file in the modules/tfa directory, or run 'drush pm:list | grep tfa' if Drush is available, or check the Drupal admin interface at /admin/modulesAffected if The version shown is less than 8.x-1.5 (e.g., 8.x-1.4, 8.x-1.3, etc.)
-
Verify the TFA module is enabledCheck the Drupal admin status report at /admin/reports/status or run 'drush pm:list --status=enabled' to confirm the tfa module is activeAffected if The TFA module is enabled and running a vulnerable version
-
Confirm TFA is configured as the authentication providerReview the user role permissions at /admin/people/permissions and check if the 'use TFA' permission is granted to any role, or inspect the TFA module configuration at /admin/config/people/tfaAffected if TFA is configured and enforced for user authentication
If the Two Factor Authentication module is enabled at a version below 8.x-1.5 and configured for user authentication, the environment is affected by this 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 · scoped8.x-1.5
Upgrade the Drupal TFA module to version 1.5.0 or later to remediate the weak authentication vulnerability.
8.x-1.5
- 1. Back up your Drupal site database and files before performing any updates.
- 2. Navigate to your Drupal admin dashboard or use Composer to update the TFA module.
- 3. Update the Two-factor Authentication (TFA) module to version 8.x-1.5 or later.
- 4. Run database updates if required (drush updatedb or via web UI).
- 5. Clear Drupal caches (drush cr).
- 6. Verify the TFA module is now running version 1.5.0 or higher and test that two-factor authentication functions correctly.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Two Factor Authentication
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13239 — 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-2024-13239 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