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

CVE-2024-13279

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 8.x-1.8 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Session Fixation vulnerability in Drupal Two-factor Authentication (TFA) allows Session Fixation.This issue affects Two-factor Authentication (TFA): from 0.0.0 before 1.8.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

Session Fixation vulnerability in Drupal Two-factor Authentication (TFA) module allows attackers to establish a known session ID before user authentication completes, then hijack the authenticated session after 2FA validation. This defeats the purpose of two-factor authentication by enabling session hijacking even with 2FA enabled.

MitigationUpgrade Two-factor Authentication (TFA) module to version 1.8.0 or later to remediate the session fixation vulnerability.

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.8

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
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 checks

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

  1. Check if the TFA module is installed
    Locate the Two-factor Authentication module in the Drupal modules directory, typically at /modules/tfa or /modules/contrib/tfa, or run 'drush pm-list --status=enabled' to list enabled modules
    Affected if The TFA module is present and enabled on the Drupal site
  2. Determine the installed TFA module version
    Check the module.info.yml or composer.json file in the TFA module directory, or run 'drush pm:info tfa' to retrieve version information
    Affected if The installed version is lower than 8.x-1.8 (e.g., 8.x-1.7, 8.x-1.6, etc.)
  3. Verify TFA is configured and active
    Check the Drupal configuration at /admin/config/people/tfa or run 'drush config-get tfa.settings' to see if TFA is enabled for user authentication
    Affected if TFA is enabled and used for user authentication on the site
  4. Confirm session handling during TFA flow
    Review the TFA module code or session configuration to verify whether session IDs are regenerated after the TFA process begins (look for session_regenerate() calls in tfa.module or related files)
    Affected if The module does not regenerate or invalidate session IDs during the two-factor authentication flow

The site is affected if the Drupal Two-factor Authentication module is installed with a version below 8.x-1.8 and TFA is enabled for user authentication.

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.8 or later
Fixed in 8.x-1.8
Interim mitigation

Upgrade Two-factor Authentication (TFA) module to version 1.8.0 or later to remediate the session fixation vulnerability.

Recommended fix High confidence

8.x-1.8

  1. Backup your Drupal site database and files
  2. Update the Two-factor Authentication (TFA) module to version 8.x-1.8 or later using Composer (composer update drupal/tfa) or the Drupal admin interface
  3. Clear Drupal caches after the update (drush cr or via admin UI)
  4. Verify the module version is 1.8.0 or higher at admin/modules
  5. Test the two-factor authentication flow to ensure it 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
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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