dbcve.org
EloquaDrupal extension · Eloqua Project

CVE-2024-13297

MEDIUM · 6.6 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 7.x-1.5 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 Eloqua allows Object Injection.This issue affects Eloqua: from 7.X-* before 7.X-1.15.

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

This is a PHP object injection vulnerability in Drupal's Eloqua integration module. The module deserializes untrusted data without proper validation, potentially allowing an attacker to inject malicious PHP objects that could lead to remote code execution if exploitable classes exist in the application stack.

MitigationUpdate Drupal Eloqua module to version 7.X-1.15 or later to patch the deserialization vulnerability. If immediate patching is not possible, consider disabling the module if Eloqua integration is not actively used.

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
EloquaDrupal extension
Affected:>= 7.x-1.0, < 7.x-1.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
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. Check if Eloqua module is installed
    List installed Drupal modules and look for any module with 'eloqua' in the name. In Drupal, you can use 'drush pm-list' or check the modules directory for the eloquent module.
    Affected if The Eloqua module files exist in the Drupal modules directory or are listed in the module list.
  2. Determine the installed version of the Eloqua module
    Run 'drush pm:list --format=json' or check the module's .info.yml file for the version number. The version should be in the format 7.x-1.x.
    Affected if The version is 7.x-1.0 through 7.x-1.4 (any version >= 7.x-1.0 but < 7.x-1.5).
  3. Verify if the module is enabled
    Check the Drupal system table or run 'drush state-get system.module' to see if the eloquent module is listed as enabled.
    Affected if The module is enabled and active on the site.
  4. Check if the module handles external data
    Review the module's configuration at /admin/config/services/eloqua or inspect any webforms or forms that integrate with Eloqua to see if they accept and process external input.
    Affected if The module is configured to accept or process data from external sources (such as webform submissions or API inputs).

You are affected if the Eloqua module is installed with a version between 7.x-1.0 and 7.x-1.4, is currently enabled, and is configured to accept external data that could be deserialized.

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.5 or later
Fixed in 7.x-1.5
Interim mitigation

Update Drupal Eloqua module to version 7.X-1.15 or later to patch the deserialization vulnerability. If immediate patching is not possible, consider disabling the module if Eloqua integration is not actively used.

Recommended fix High confidence

7.x-1.15

  1. Back up your Drupal site database and files before making any changes
  2. Update the Eloqua module to version 7.x-1.15 or later using Composer (composer require drupal/eloqua:^7.x-1.15) or through the Drupal admin UI
  3. Clear the Drupal cache after updating (drush cr or via admin UI)
  4. Verify the Eloqua module is updated to 7.x-1.15 in the modules list
  5. Test that the Eloqua integration is functioning correctly after the update

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

Fix this in Eloqua Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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