# CVE-2024-13259: Image Sizes - Moderately critical - Access bypass - SA-CONTRIB-2024-023

> Attackers can access sensitive information via forceful browsing in the Drupal Image Sizes module, requiring an upgrade to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jan 2025
- **Updated:** 10 Jan 2025
- **Also known as:** DRUPAL-CONTRIB-2024-023, GHSA-qffj-hqp2-qrxm

## What is CVE-2024-13259?

CVE-2024-13259 is a high-severity vulnerability in Drupal Image Sizes, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insertion of Sensitive Information Into Sent Data vulnerability in Drupal Image Sizes allows Forceful Browsing.This issue affects Image Sizes: from 0.0.0 before 3.0.2.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/image_sizes` | Packagist:https://packages.drupal.org/8 | All versions | 3.0.2 |

Products: Image Sizes Project Image Sizes.

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

Upgrade to a fixed version.

## Is CVE-2024-13259 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13259 is a high-severity vulnerability in Drupal Image Sizes, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13259 in the wild and no public exploit code.

Affected product: Drupal Image Sizes. 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-13259/ (Markdown: https://insights.sbomify.com/CVE-2024-13259/index.md)
```

## Sources

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

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