Skip to content

tarteaucitron.js allows url scheme injection via unfiltered inputs

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, allowing a user with high privileges (access to the site's source code or a CMS plugin) to enter a URL containing an insecure scheme such as javascript:alert(). Before the fix, URL validation was insufficient, which could allow arbitrary JavaScript execution if a user clicked on a malicious link.

Impact

An attacker with high privileges could insert a link exploiting an insecure URL scheme, leading to:

  • Execution of arbitrary JavaScript code
  • Theft of sensitive data through phishing attacks
  • Modification of the user interface behavior

Fix AmauriC/tarteaucitron.js@2fa1e01

The issue was resolved by enforcing strict URL validation, ensuring that they start with http:// or https:// before being used.

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
Required
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:R/S:C/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(11th percentile)

Weaknesses

CVE ID

CVE-2025-31476

GHSA ID

GHSA-p5g4-v748-6fh8

Source code

Credits

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