# CVE-2024-13304: Minify JS - Moderately critical - Cross site request forgery - SA-CONTRIB-2024-070

> Attackers can trick authenticated users into performing unwanted actions in the Drupal Minify JS module via CSRF.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Jan 2025
- **Updated:** 10 Jan 2025
- **Also known as:** DRUPAL-CONTRIB-2024-070, GHSA-6hq6-3pp3-9598

## What is CVE-2024-13304?

CVE-2024-13304 is a medium-severity vulnerability in Drupal Minify JS, published on 9 Jan 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in Drupal Minify JS allows Cross Site Request Forgery.This issue affects Minify JS: from 0.0.0 before 3.0.3.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


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

Products: Matthiasmullie Minify Js.

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

Upgrade to a fixed version.

## Is CVE-2024-13304 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13304 is a medium-severity vulnerability in Drupal Minify JS, published on 9 Jan 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-13304 in the wild and no public exploit code.

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

## Sources

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

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