Skip to content

tarteaucitron.js allows prototype pollution via custom text injection

Moderate severity GitHub Reviewed Published Apr 7, 2025 in AmauriC/tarteaucitron.js • Updated Apr 7, 2025

Package

npm tarteaucitronjs (npm)

Affected versions

< 1.20.1

Patched versions

1.20.1

Description

A vulnerability was identified in tarteaucitron.js, 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.

Impact

An attacker with high privileges could exploit this vulnerability to:

  • Modify object prototypes, affecting core JavaScript behavior,
  • Cause application crashes or unexpected behavior,
  • Potentially introduce further security vulnerabilities depending on the application's architecture.

Fix AmauriC/tarteaucitron.js@74c354c

The issue was resolved by ensuring that user-controlled inputs cannot modify JavaScript object prototypes.

References

@AmauriC AmauriC published to AmauriC/tarteaucitron.js Apr 7, 2025
Published by the National Vulnerability Database Apr 7, 2025
Published to the GitHub Advisory Database Apr 7, 2025
Reviewed Apr 7, 2025
Last updated Apr 7, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

EPSS score

Weaknesses

CVE ID

CVE-2025-31475

GHSA ID

GHSA-4hwx-xcc5-2hfc

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.