dbcve.org
Monster MenusDrupal extension · Monster Menus Project

CVE-2024-13281

CRITICAL · 9.1 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 7.x-1.34 / 9.3.2 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 Monster Menus allows Forceful Browsing.This issue affects Monster Menus: from 0.0.0 before 9.3.2.

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 confidence

An incorrect authorization vulnerability in Drupal Monster Menus module allows forceful browsing, enabling attackers to access restricted content or administrative functions by directly requesting URLs they should not have access to, bypassing intended access controls.

MitigationUpgrade Monster Menus to version 9.3.2 or later to remediate the authorization bypass. If immediate upgrade is not possible, review and restrict access controls on Monster Menus configurations.

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
Monster MenusDrupal extension
Affected:< 7.x-1.34>= 9.3.0, < 9.3.2

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. Identify if Monster Menus module is installed
    Check the Drupal modules directory (sites/all/modules or web/modules/contrib) for the monster_menus folder, or run `drush pm-list --type=module` and look for Monster Menus in the output
    Affected if The Monster Menus module is present in the Drupal installation
  2. Determine the installed Monster Menus version
    Check the version in the module's .info.yml file (e.g., monster_menus.info.yml) under the version: field, or run `drush pm:security` to see installed module versions, or query the Drupal system table in the database for the monster_menus module entry
    Affected if The installed version is 7.x-1.34 or lower, OR the version is 9.3.0 or 9.3.1
  3. Confirm the Monster Menus configuration is active
    Check if Monster Menus is enabled in Drupal's module administration page, or query the system table where type='module' and name='monster_menus' and status=1, or verify the module appears in the enabled modules list
    Affected if Monster Menus module is installed and enabled in the Drupal site
  4. Inspect Monster Menus access control configurations
    Review the Monster Menus configuration at admin/config/content/monster-menus (or similar path) to identify which content types or menus are managed by Monster Menus and note any restricted access settings
    Affected if Monster Menus is configured to manage content or menus with access restrictions

The environment is affected if Monster Menus module is installed and enabled with an installed version below 7.x-1.34 or at 9.3.0-9.3.1, and the module is configured to control access to content or administrative functions.

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.34 / 9.3.2 or later
Fixed in 7.x-1.349.3.2
Interim mitigation

Upgrade Monster Menus to version 9.3.2 or later to remediate the authorization bypass. If immediate upgrade is not possible, review and restrict access controls on Monster Menus configurations.

Recommended fix High confidence

Monster Menus 7.x-1.34 or 9.3.2 (depending on your Drupal version)

  1. 1. Identify which version branch of Monster Menus is installed (7.x or 9.x)
  2. 2. If using Drupal 7 with Monster Menus 7.x, upgrade to version 7.x-1.34 or later
  3. 3. If using Drupal 9+ with Monster Menus 9.x, upgrade to version 9.3.2 or later
  4. 4. Run database updates via drush updatedb or through the web interface at /update.php
  5. 5. Clear all Drupal caches (drush cr)
Caveat Review release notes at www.drupal.org/project/monster_menus for any configuration or API changes between your current version and the target version

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

Fix this in Monster Menus Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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