dbcve.org
Smart Ip BanDrupal extension · Smart Ip Ban Project

CVE-2024-13277

CRITICAL · 9.1 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 7.x-1.1 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
Incorrect Authorization vulnerability in Drupal Smart IP Ban allows Forceful Browsing.This issue affects Smart IP Ban: from 7.X-1.0 before 7.X-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

The Drupal Smart IP Ban module versions 7.X-1.0 through before 7.X-1.1 contain an Incorrect Authorization vulnerability that allows forceable browsing attacks, enabling unauthenticated or unauthorized users to bypass access controls and access restricted resources or functionality.

MitigationUpdate the Smart IP Ban module to version 7.X-1.1 or later to obtain the authorization fix. Before deploying to production, verify that access controls properly enforce authorization across all restricted paths.

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
Smart Ip BanDrupal extension
Affected:>= 7.x-1.0, < 7.x-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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Verify Smart IP Ban module is installed
    Check the Drupal modules directory for the smart_ip_ban module, or run 'drush pm-list --status=enabled' to list enabled modules
    Affected if The Smart IP Ban module is present and enabled on the Drupal installation
  2. Determine the installed version of Smart IP Ban
    Check the module's info file (smart_ip_ban.info) or run 'drush pm-info smart_ip_ban' to retrieve the exact version number
    Affected if The version returned is 7.x-1.0 or any version between 7.x-1.0 and 7.x-1.1 (excluding 7.x-1.1)
  3. Confirm the module is in the affected version range
    Compare the installed version against the affected range: version >= 7.x-1.0 AND version < 7.x-1.1
    Affected if The installed version satisfies both conditions: it is 7.x-1.0 or higher but earlier than 7.x-1.1
  4. Identify restricted resources or paths
    Review Drupal permissions and access control settings for the Smart IP Ban module, check for admin paths or restricted IP ban functionality
    Affected if The module provides restricted administrative paths or access-controlled features that could be bypassed

A user is affected if the Smart IP Ban module is installed with version 7.x-1.0 through any version before 7.x-1.1, as this version range contains the Incorrect Authorization vulnerability that allows access control bypass.

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

Update the Smart IP Ban module to version 7.X-1.1 or later to obtain the authorization fix. Before deploying to production, verify that access controls properly enforce authorization across all restricted paths.

Recommended fix High confidence

7.x-1.1

  1. 1. Back up your Drupal site database and files before performing any updates.
  2. 2. Navigate to your Drupal administration panel and go to Extend > Smart IP Ban module.
  3. 3. Click on the 'Update' button for Smart IP Ban, or use Composer: run 'composer update drupal/smart_ip_ban' in your project root.
  4. 4. Verify the module has been updated to version 7.x-1.1 by checking the module's info in Extend or via 'drush pm-list | grep smart_ip_ban'.
  5. 5. Clear Drupal cache: run 'drush cr' or access admin/config/development/performance and clear caches.
  6. 6. Test that the Smart IP Ban functionality works correctly and that the authorization vulnerability is resolved.

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

Fix this in Smart Ip Ban Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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