dbcve.org
Basic Http AuthenticationDrupal extension · Basic Http Authentication Project

CVE-2024-13291

HIGH · 7.3 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 7.x-1.4 or later.
See remediation →
82/100
Remediation priority · High
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
Incorrect Authorization vulnerability in Drupal Basic HTTP Authentication allows Forceful Browsing.This issue affects Basic HTTP Authentication: from 7.X-1.0 before 7.X-1.4.

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

The Basic HTTP Authentication module for Drupal 7.x contains an incorrect authorization vulnerability that allows forceful browsing. This means authenticated users can access resources or administrative paths they should not have permission to access, bypassing role-based access controls. The vulnerability exists in versions 7.X-1.0 through 7.X-1.3, with the fix available in version 7.X-1.4.

MitigationUpdate the Basic HTTP Authentication module to version 7.X-1.4 or later to patch the authorization bypass. After updating, verify that role-based access controls properly restrict access to protected resources and administrative functions.

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
Basic Http AuthenticationDrupal extension
Affected:< 7.x-1.4

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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. Locate the Basic HTTP Authentication module in your Drupal installation
    Check your Drupal modules directory (sites/all/modules or sites/[sitename]/modules) for a folder named 'basic_http_authentication' or similar. Alternatively, query your Drupal database: SELECT name, status FROM system WHERE name LIKE '%basic%http%auth%';
    Affected if The module folder or database entry exists and the module is installed.
  2. Determine the installed version of the Basic HTTP Authentication module
    Check the .info file in the module directory for the version line, or run: drush pm-list --filter=basic_http_authentication. If drush is unavailable, inspect the module's .info file content for the version field.
    Affected if The version is 7.X-1.0, 7.X-1.1, 7.X-1.2, or 7.X-1.3 (any version below 7.X-1.4).
  3. Verify the module is enabled on your site
    Query the system table: SELECT * FROM system WHERE name LIKE '%basic%http%' AND type='module' AND status=1; Or use Drush: drush state-get system.module_list (if basic_http_authentication appears, it is enabled).
    Affected if The module is enabled (status = 1) and the version is below 7.X-1.4.
  4. Check for existing role-based access control misconfigurations
    Review your Drupal permissions at admin/people/permissions. Specifically verify that authenticated users do not have unintended access to administrative paths. This vulnerability allows bypass of role restrictions, so review paths under admin/ that should be restricted to administrator roles only.
    Affected if Authenticated users can access administrative paths or resources they should not reach, indicating the authorization bypass is present.

You are affected if the Basic HTTP Authentication module is installed and enabled with any version below 7.X-1.4, and users can access resources or administrative paths that violate your role-based access control settings.

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

Update the Basic HTTP Authentication module to version 7.X-1.4 or later to patch the authorization bypass. After updating, verify that role-based access controls properly restrict access to protected resources and administrative functions.

Recommended fix High confidence

7.x-1.4

  1. Backup your Drupal site database and files before proceeding
  2. Navigate to the Drupal project page for Basic HTTP Authentication at www.drupal.org/project/basic_http_authentication
  3. Download version 7.x-1.4 of the module
  4. Extract the archive and replace the existing basic_http_authentication module directory in your Drupal installation (typically at /modules or /sites/all/modules)
  5. Run database updates if required: drush updatedb or visit /update.php
  6. Clear Drupal caches: drush cache-clear all or through the admin interface
  7. Verify the module is updated to version 7.x-1.4 on the Extend (Modules) page

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

Fix this in Basic Http Authentication Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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