# CVE-2024-13297: Eloqua - Moderately critical - Arbitrary PHP code execution - SA-CONTRIB-2024-063

> An attacker can execute arbitrary PHP code via unsafe deserialization in the Drupal Eloqua module, requiring an upgrade to patch.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2025
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-rj9h-wxr6-mwg8

## What is CVE-2024-13297?

CVE-2024-13297 is a medium-severity unsafe deserialization vulnerability in Drupal Eloqua, published on 9 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Deserialization of Untrusted Data vulnerability in Drupal Eloqua allows Object Injection.This issue affects Eloqua: from 7.X-* before 7.X-1.15.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-13297?

It affects 1 product.


Products: Eloqua Project Eloqua.

## How do I fix CVE-2024-13297?

No fix has been published for CVE-2024-13297 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-13297 being exploited?

There is no known exploitation of CVE-2024-13297 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13297 and fix it if it is affected.

What it is: CVE-2024-13297 is a medium-severity unsafe deserialization vulnerability in Drupal Eloqua, published on 9 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13297 in the wild and no public exploit code.

Affected product: Drupal Eloqua. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-13297/ (Markdown: https://insights.sbomify.com/CVE-2024-13297/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-13297
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-13297
- OSV: https://osv.dev/vulnerability/CVE-2024-13297

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-13297/
Summaries are generated and may contain mistakes; the official description above is the record.