Block PermissionsDrupal extension · Block Permissions Project
CVE-2024-13282
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 · uneditedIncorrect Authorization vulnerability in Drupal Block permissions allows Forceful Browsing.This issue affects Block permissions: from 1.0.0 before 1.2.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 confidenceIncorrect Authorization vulnerability in Drupal's Block permissions module allows Forceful Browsing, enabling authenticated users to access blocks they should not have permission to view or manipulate. This affects versions 1.0.0 through versions before 1.2.0.
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
Block PermissionsDrupal extension
>= 1.0.0, < 1.2.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify if Block Permissions module is installedIn Drupal, check the module list via admin interface at /admin/modules or by inspecting the modules directory for the 'block_permissions' module folderAffected if The block_permissions module exists in the Drupal installation
-
Determine the installed version of Block PermissionsCheck the block_permissions.info.yml file in the module directory, or view the version via Drupal's admin interface at /admin/modules (version column), or run: drush pm-list --filter=block_permissionsAffected if The installed version is 1.0.0, 1.0.x, 1.1.x, or any version >= 1.0.0 and < 1.2.0
-
Verify block permissions configuration existsInspect the permission configuration at /admin/people/permissions#module-block_permissions or check the permission table in the database for entries related to block_permissionsAffected if Custom block-specific permissions are defined and assigned to users or roles
The environment is affected if the Block Permissions module is installed with a version between 1.0.0 and 1.1.x inclusive, and custom block permissions are in use.
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 · scoped1.2.0
Upgrade the Block permissions module to version 1.2.0 or later to address the authorization bypass.
1.2.0
- 1. Back up your Drupal site database and files
- 2. Update the Block permissions module to version 1.2.0 via Composer (composer update drupal/block_permissions) or the Drupal UI
- 3. Clear Drupal caches (drush cr or via admin UI)
- 4. Verify the update was successful and test that block permission controls work correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Block Permissions
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13282 — 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-13282 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