dbcve.org
Migrate ToolsDrupal extension · Migrate Tools Project

CVE-2024-13244

HIGH · 8.8 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 6.0.3 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 Migrate Tools allows Cross Site Request Forgery.This issue affects Migrate Tools: from 0.0.0 before 6.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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in Drupal Migrate Tools allows remote attackers to induce authenticated users into performing unintended migration operations through maliciously crafted requests. The vulnerability exists in versions prior to 6.0.3, potentially allowing attackers to manipulate or execute migration processes without proper anti-CSRF token validation.

MitigationUpdate Drupal Migrate Tools to version 6.0.3 or later to obtain the CSRF protection fixes. Review migration configurations for any unauthorized changes after applying the update.

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
Migrate ToolsDrupal extension
Affected:>= 6.0.0, < 6.0.3>= 8.x-1.0, <= 8.x-5.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
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. Verify Migrate Tools module is installed
    Run 'drush pm-list' or check the Drupal modules directory for the migrate_tools module in /modules/contrib/migrate_tools/
    Affected if The module is present in the Drupal installation
  2. Determine the installed version of Migrate Tools
    Run 'drush pm:list --filter=migrate_tools' or check the module's .info.yml file for the version number
    Affected if Version number is returned from the module
  3. Compare version against affected ranges
    Check if version is >= 6.0.0 and < 6.0.3, OR >= 8.x-1.0 and <= 8.x-5.2
    Affected if Installed version falls within any of these ranges: 6.0.0 through 6.0.2, or 8.x-1.0 through 8.x-5.2
  4. Confirm module is enabled for migrations
    Check if the migrate_tools module is enabled in Drupal by running 'drush state:get system.module_enabled' or viewing the module administration page
    Affected if The module is enabled and functional in a live Drupal environment

A user is affected if the Migrate Tools module is installed and enabled with a version matching >= 6.0.0 and < 6.0.3 OR >= 8.x-1.0 and <= 8.x-5.2

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 6.0.3 or later
Fixed in 6.0.3
Interim mitigation

Update Drupal Migrate Tools to version 6.0.3 or later to obtain the CSRF protection fixes. Review migration configurations for any unauthorized changes after applying the update.

Recommended fix Moderate confidence

6.0.3 for 6.x branch; 8.x-6.0 or later for 8.x branch

  1. 1. Identify the currently installed version of Migrate Tools: composer show drupal/migrate_tools
  2. 2. For Drupal 9/10 (6.x line): Run 'composer require drupal/migrate_tools:6.0.3' to upgrade to the fixed version
  3. 3. For Drupal 8 (8.x line): Run 'composer require drupal/migrate_tools:8.x-6.0' or 'composer update drupal/migrate_tools' to get the latest stable 8.x release that includes the fix
  4. 4. Clear Drupal caches: drush cr or drupal cache:clear
  5. 5. Run database updates if required: drush updb
  6. 6. Verify the new version is installed: composer show drupal/migrate_tools
Caveat Ensure PHP version compatibility and review any migrate configuration changes between versions before deploying to production

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

Fix this in Migrate Tools Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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 locally
dbcve dependency scanner

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