dbcve.org
MailjetDrupal extension

CVE-2024-13296

MEDIUM · 6.6 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 4.0.1 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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
Deserialization of Untrusted Data vulnerability in Drupal Mailjet allows Object Injection.This issue affects Mailjet: from 0.0.0 before 4.0.1.

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

The Drupal Mailjet module contains a deserialization vulnerability where untrusted data is passed to PHP's unserialize() function, allowing an attacker to inject PHP objects and potentially achieve remote code execution. This occurs in the Mailjet integration module before version 4.0.1.

MitigationUpdate the Drupal Mailjet module to version 4.0.1 or later to remediate this vulnerability. As a defensive measure, ensure the Drupal installation is on a patched version and restrict access to any Mailjet-related 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
MailjetDrupal extension
Affected:< 4.0.1

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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/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 Mailjet module installation
    Check your Drupal installation's modules directory for the Mailjet module folder (commonly sites/all/modules/contrib/mailjet or modules/contrib/mailjet). Verify the directory exists and contains module files.
    Affected if The Mailjet module directory is present in your Drupal modules folder.
  2. Determine the installed Mailjet module version
    Open the mailjet.info.yml file (or mailjet.module) within the Mailjet module directory and read the 'version' or 'core' and version fields. Alternatively, check composer.json if present for the 'version' entry under 'require' for the drupal/mailjet package.
    Affected if The version listed is below 4.0.1 (for example: 4.0.0, 3.x.x, or any version prior to 4.0.1).
  3. Identify if the vulnerable deserialization code path is reachable
    Search the Mailjet module PHP files for usages of unserialize() function, particularly where user-supplied input (such as $_GET, $_POST, $_REQUEST, or request parameters) is passed as the input. Common locations include form handlers, webhook callbacks, or API controllers.
    Affected if Code exists that passes untrusted input directly to unserialize() and the module version is below 4.0.1.
  4. Check for exposure of Mailjet-related URLs
    Review your web server logs or Drupal routing configuration for access to Mailjet-related endpoints (paths containing 'mailjet', webhook handlers, or callback URLs). Examine if these endpoints are externally accessible without authentication safeguards.
    Affected if Mailjet module endpoints are accessible externally and the module version is below 4.0.1.

You are affected if the Mailjet module is installed at a version below 4.0.1 AND the vulnerable unserialize() code path with untrusted input is accessible in your environment.

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

Update the Drupal Mailjet module to version 4.0.1 or later to remediate this vulnerability. As a defensive measure, ensure the Drupal installation is on a patched version and restrict access to any Mailjet-related endpoints.

Recommended fix High confidence

4.0.1

  1. 1. Backup your Drupal site database and files before performing any updates
  2. 2. Update the Mailjet Drupal module to version 4.0.1 using Composer: `composer require drupal/mailjet:^4.0.1` or via the Drupal administrative interface at /admin/modules
  3. 3. Run database updates if prompted: `drush updatedb` or via the administrative interface at /admin/reports/status
  4. 4. Clear Drupal caches: `drush cr` or via the administrative interface at /admin/config/development/performance
  5. 5. Verify the module is now running version 4.0.1 at /admin/reports/status
Caveat No specific breaking changes documented in the provided advisory

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

Fix this in Mailjet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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