dbcve.org
Login DisableDrupal extension · Login Disable Project

CVE-2024-13309

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Improper Authentication vulnerability in Drupal Login Disable allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Login Disable: from 2.0.0 before 2.1.1.

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

Improper authentication vulnerability in Drupal's Login Disable module (versions 2.0.0 through 2.1.0) allows attackers to exploit incorrectly configured access control security levels, potentially bypassing authentication controls intended to restrict login access.

MitigationUpgrade Login Disable module to version 2.1.1 or later to obtain the security patch that corrects the improper authentication handling and access control configuration.

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
Login DisableDrupal extension
Affected:>= 2.0.0, < 2.1.1

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check if Login Disable module is installed
    Run 'drush pm-list' or inspect the modules directory for the login_disable module. In Drupal admin, check /admin/modules for the Login Disable module.
    Affected if The Login Disable module is present in the Drupal installation
  2. Verify the installed version of Login Disable
    Run 'drush pm:list --filter=login_disable' or check the info.yml file (login_disable.info.yml) in the module directory for the 'version' field.
    Affected if The installed version is >= 2.0.0 and < 2.1.1 (e.g., 2.0.0, 2.0.1, 2.1.0)
  3. Confirm the module is enabled
    Run 'drush state:get system.module_enabled' or check the module's status in /admin/modules. The vulnerability only applies when the module is actively enabled.
    Affected if The Login Disable module is enabled and active in the Drupal site
  4. Review access control configuration
    Inspect the module configuration at /admin/config/people/login-disable or check the login_disable configuration in the config table. Look for access control settings related to login restrictions.
    Affected if Login Disable access control rules are configured (the vulnerability exploits incorrect configuration of these rules)

A site is affected if it has Login Disable module version 2.0.0-2.1.0 installed and enabled with access control rules configured.

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 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade Login Disable module to version 2.1.1 or later to obtain the security patch that corrects the improper authentication handling and access control configuration.

Recommended fix High confidence

2.1.1

  1. 1. Back up your Drupal site database and files
  2. 2. Navigate to your Drupal project root directory
  3. 3. Update the Login Disable module using Composer: composer update drupal/login_disable --with-all-dependencies
  4. 4. Alternatively, download version 2.1.1 from www.drupal.org/project/login_disable and upload to web/modules directory
  5. 5. Run Drupal database updates: drush updatedb or navigate to /update.php
  6. 6. Clear Drupal caches: drush cache-rebuild or through admin UI

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

Fix this in Login Disable Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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