tarteaucitron.js allows url scheme injection via unfiltered inputs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2025-31476: 0.36% estimated exploitation activity in the next 30 days; percentile 29.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 https://github.com/AmauriC/tarteaucitron.js/commit/2fa1e01023bce2e4b813200600bb1619d56ceb02 The issue was resolved by enforcing strict URL validation, ensuring that they start with http:// or https:// before being used.

Published by the source

7 Apr 2025, 16:46 UTC

Last modified by the source

10 Dec 2025, 23:41 UTC

Source last checked

26 Oct 2026, 12:36 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p5g4-v748-6fh8

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-p5g4-v748-6fh8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-31476

Advisory: tarteaucitron.js allows url scheme injection via unfiltered inputs
IDs: CVE-2025-31476, GHSA-p5g4-v748-6fh8
Record: https://patchnext.com/advisories/cve-2025-31476 (revision 2, source checked 26 Oct 2026, 12:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tarteaucitronjs 1.20.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm tarteaucitronjs: affected < 1.20.1; fixed in 1.20.1

## Suggested inspection (read-only)
- `npm ls tarteaucitronjs --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tarteaucitronjs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-p5g4-v748-6fh8 (OSV record GHSA-p5g4-v748-6fh8 lists affected ranges: npm tarteaucitronjs >=0 <1.20.1 (fixed))
- Verified: https://github.com/advisories/GHSA-p5g4-v748-6fh8 (GitHub-reviewed advisory GHSA-p5g4-v748-6fh8 lists affected ranges: npm tarteaucitronjs >=0 <1.20.1)

Commands are suggestions: review each one before running it.