dbcve.org
GutenbergDrupal extension · Drupalgutenberg

CVE-2024-13284

HIGH · 8.8 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 2.13.0 / 3.0.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Drupal Gutenberg allows Cross Site Request Forgery.This issue affects Gutenberg: from 0.0.0 before 2.13.0, from 3.0.0 before 3.0.5.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Drupal Gutenberg module allows attackers to trick authenticated users into executing unintended actions on the Drupal site. The vulnerability affects Gutenberg versions before 2.13.0 and before 3.0.5.

MitigationUpgrade Drupal Gutenberg to version 2.13.0 or 3.0.5 or later to implement anti-CSRF token validation in affected forms and endpoints.

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
GutenbergDrupal extension
Affected:< 2.13.0>= 3.0.0, < 3.0.5

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Gutenberg module directory
    In your Drupal installation, navigate to the modules directory (typically /modules/ or /sites/all/modules/) and locate the 'gutenberg' or 'drupalgutenberg' folder.
    Affected if The folder exists and contains the Gutenberg module files.
  2. Find the module version information
    Open the gutenberg.info.yml or drupalgutenberg.info.yml file located in the module directory. Look for the 'version' or 'core' field to identify the installed version.
    Affected if A version number is present in the .info.yml file.
  3. Compare installed version to affected ranges
    Check if the installed version is less than 2.13.0, or greater than or equal to 3.0.0 but less than 3.0.5. These are the vulnerable version ranges.
    Affected if The installed version falls into < 2.13.0 or >= 3.0.0, < 3.0.5.
  4. Verify the site uses the Gutenberg module
    Log in to the Drupal administration panel and navigate to the Extend or Modules page. Confirm that the Gutenberg module is enabled and active.
    Affected if The Gutenberg module is installed and enabled.

A user is affected if the Drupal Gutenberg module is enabled and its installed version is less than 2.13.0 or between 3.0.0 and 3.0.5.

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 2.13.0 / 3.0.5 or later
Fixed in 2.13.03.0.5
Interim mitigation

Upgrade Drupal Gutenberg to version 2.13.0 or 3.0.5 or later to implement anti-CSRF token validation in affected forms and endpoints.

Recommended fix High confidence

Gutenberg 2.13.0 or later, or Gutenberg 3.0.5 or later

  1. 1. Back up your Drupal site database and files.
  2. 2. If using Gutenberg 2.x line, upgrade to version 2.13.0 or later.
  3. 3. If using Gutenberg 3.x line, upgrade to version 3.0.5 or later.
  4. 4. In Drupal admin, navigate to Extend or the module management page.
  5. 5. Check for updates for the Gutenberg module and apply the update.
  6. 6. Run database updates if prompted (drush updatedb or through admin UI).
  7. 7. Clear Drupal caches (drush cr).
  8. 8. Verify the Gutenberg module is working correctly after upgrade.

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

Fix this in Gutenberg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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