Pages Restriction AccessDrupal extension · Ciandt
CVE-2024-13302
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 Pages Restriction Access allows Forceful Browsing.This issue affects Pages Restriction Access: from 2.0.0 before 2.0.3.
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 confidenceThe Pages Restriction Access Drupal module before 2.0.3 contains an incorrect authorization vulnerability that allows forceful browsing, meaning users can access restricted pages by directly navigating to URLs that should be protected, bypassing the module's access control checks.
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
Pages Restriction AccessDrupal extension
>= 2.0.0, < 2.0.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Pages Restriction Access module is installedLocate the Ciandt Pages Restriction Access module directory in your Drupal installation (typically under modules/contrib or sites/all/modules) or check via Drupal admin UI at Extend listAffected if The module directory or entry exists in the Drupal modules folder
-
Determine the installed module versionOpen the pages_restriction_access.info.yml file inside the module directory and read the 'version' or 'core_version' value, or check the version displayed in Drupal's Extend administration pageAffected if The version listed is 2.0.0, 2.0.1, or 2.0.2 (any version >= 2.0.0 but < 2.0.3)
-
Confirm the module is enabledCheck Drupal's Extend page or run 'drush pm-list --status=enabled' to verify pages_restriction_access module is currently enabledAffected if The module shows as enabled in Drupal's module administration
-
Verify restricted pages are configuredInspect the module's configuration at Configuration > Pages Restriction Access (or equivalent path) to see if any page restrictions are definedAffected if Any restricted page paths or patterns exist in the module's configuration settings
You are affected if the Pages Restriction Access module is installed with version 2.0.0, 2.0.1, or 2.0.2, is currently enabled, and has restricted pages configured.
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 · scoped2.0.3
Update Pages Restriction Access module to version 2.0.3 or later to obtain the vendor fix for the authorization bypass.
2.0.3
- Backup your Drupal site database and files before making any changes
- Update the Pages Restriction Access module to version 2.0.3 or later using Composer (composer update drupal/pages_restriction_access) or via the Drupal admin interface at /admin/modules
- Clear Drupal caches after the update using drush cr or through the admin interface at /admin/config/development/performance
- Verify that the Pages Restriction Access functionality works correctly and that the authorization controls are functioning as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pages Restriction Access
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13302 — 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-13302 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