CVE-2024-13266
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 Responsive and off-canvas menu allows Forceful Browsing.This issue affects Responsive and off-canvas menu: from 0.0.0 before 4.4.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 confidenceThe Drupal 'Responsive and off-canvas menu' module versions before 4.4.4 contain an incorrect authorization vulnerability that allows forceful browsing, potentially enabling unauthenticated or low-privileged users to access menu resources or pages they should not be able to reach.
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< 4.4.4CVSS 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.
-
Locate the Responsive and off-canvas menu module installationSearch the Drupal modules directory (typically /modules/contrib/ or /web/modules/contrib/) for a folder named 'responsive_menu' or 'responsive_and_off_canvas_menu'. If using Composer, check composer.json for a require entry containing 'responsive_menu' or the module name.Affected if The module directory or composer entry is found in the Drupal installation.
-
Determine the installed module versionOpen the .info.yml file inside the module directory and read the 'version' field, or check the composer.json file for the version number listed under 'require'.Affected if The version number found is lower than 4.4.4 (for example, 4.4.3, 4.4.0, or any version without a number).
-
Verify the module is enabled on the siteRun 'drush pm-list --status=enabled' or access the Drupal admin UI at /admin/modules to confirm the module is listed as enabled. Alternatively, query the 'system' database table where type='module' and name contains 'responsive'.Affected if The module shows status as 'Enabled' in Drush, the admin UI, or the database.
-
Confirm the module is providing menu functionalityAccess the Drupal site configuration at /admin/config/user-interface/responsive-menu (or similar path under /admin/config) to verify the menu module has active menu configurations. Check if any menu is assigned to display via the responsive menu settings.Affected if There are active menu configurations using this module for front-end display.
If the Responsive and off-canvas menu module is installed, enabled, actively providing menu resources, and its version is below 4.4.4, the site is affected by this authorization bypass vulnerability.
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 · scoped4.4.4
Update the Responsive and off-canvas menu module to version 4.4.4 or later to resolve the authorization bypass. Review user role permissions after updating.
4.4.4
- Backup your Drupal site database and files before proceeding
- Update the Responsive and off-canvas menu module using Composer: run 'composer update drupal/responsive_menu --with-all-dependencies' or download version 4.4.4 from www.drupal.org
- After updating, run Drupal database updates: 'drush updatedb' or via the admin interface at /update.php
- Clear Drupal caches: run 'drush cr' or clear caches via the admin interface at /admin/config/development/performance
- Verify the module is updated to version 4.4.4 by checking the module's info at /admin/modules
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13266 — 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-13266 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