# CVE-2025-31475: tarteaucitron.js allows prototype pollution via custom text injection

> Attackers with source code access can inject malicious prototypes in tarteaucitron.js, potentially causing code execution or application crashes.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2025
- **Updated:** 7 Apr 2025
- **Also known as:** GHSA-4hwx-xcc5-2hfc

## What is CVE-2025-31475?

CVE-2025-31475 is a medium-severity code injection vulnerability in AmauriC tarteaucitron.js, published on 7 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

tarteaucitron.js is a compliant and accessible cookie banner. A vulnerability was identified in tarteaucitron.js prior to 1.20.1, where the addOrUpdate function, used for applying custom texts, did not properly validate input. This allowed an attacker with direct access to the site's source code or a CMS plugin to manipulate JavaScript object prototypes, leading to potential security risks such as data corruption or unintended code execution. An attacker with high privileges could exploit this vulnerability to modify object prototypes, affecting core JavaScript behavior, cause application crashes or unexpected behavior, or potentially introduce further security vulnerabilities depending on the application's architecture. This vulnerability is fixed in 1.20.1.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2025-31475?

2 open source packages ship an affected version, including tarteaucitronjs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tarteaucitronjs` | npm | All versions | 1.20.1 |
| `tarteaucitronjs` | npm | All versions | 1.20.1 |

Products: Amauri Tarteaucitronjs.

## How do I fix CVE-2025-31475?

Upgrade tarteaucitronjs to 1.20.1 or later.

## Is CVE-2025-31475 being exploited?

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

## Other vulnerabilities in AmauriC tarteaucitron.js

- [CVE-2025-31138](https://insights.sbomify.com/CVE-2025-31138/): tarteaucitron.js allows UI manipulation via unrestricted CSS injection (medium 5.5)
- [CVE-2025-31476](https://insights.sbomify.com/CVE-2025-31476/): tarteaucitron.js allows url scheme injection via unfiltered inputs (medium 4.8)
- [CVE-2026-22809](https://insights.sbomify.com/CVE-2026-22809/): tarteaucitron.js has Regular Expression Denial of Service (ReDoS) vulnerability (medium 4.4)
- [CVE-2025-48939](https://insights.sbomify.com/CVE-2025-48939/): tarteaucitron.js vulnerable to DOM Clobbering via document.currentScript (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31475 and fix it if it is affected.

What it is: CVE-2025-31475 is a medium-severity code injection vulnerability in AmauriC tarteaucitron.js, published on 7 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31475 in the wild and no public exploit code.

Affected packages and fixed versions:
- tarteaucitronjs (npm): affected all versions; fixed in 1.20.1
- tarteaucitronjs (npm): affected all versions; fixed in 1.20.1

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-2025-31475/ (Markdown: https://insights.sbomify.com/CVE-2025-31475/index.md)
```

## Sources

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

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