Skip to content

← Public intelligence

npm package

tarteaucitronjs

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

8 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.3npmAmendedPublished

    tarteaucitron: data-cookie attribute can be used to delete arbitrary cookies

    CVE-2026-49977 · GHSA-jxj7-g6gm-49j7

    Affected
    • npm tarteaucitronjs < 1.33.0
    Fixed in
    1.33.0· Vendor fix available
    Issue
    tarteaucitron provides a list of cookies and buttons to delete them. If an attacker can write HTML with data attributes, they could create an element that silently deletes a cookie when clicked and trick a user to delete this cookie. Details tarteaucitron.cookie.purge() is called on any element with the purgeBtn class. It does not check if the element is a legitimate tarteaucitron button or if the cookie corresponds to a service handled by tarteaucitron. PoC If someone has a cookie with this name and clicks on the link, the cookie is silently deleted. Impact The impact is limited because this only works on cookies without HttpOnly=true and the attacker has to know the name of the cookie.

    Recommended action: Upgrade to 1.33.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. Medium, CVSS 4.4npmAmendedPublished

    tarteaucitron.js has Regular Expression Denial of Service (ReDoS) vulnerability

    CVE-2026-22809 · GHSA-q5f6-qxm2-mcqm

    Affected
    • npm tarteaucitronjs < 1.29.0
    Fixed in
    1.29.0· Vendor fix available
    Issue
    A potential Regular Expression Denial of Service (ReDoS) vulnerability was identified in tarteaucitron.js in the handling of the issuuid parameter. Details The issue was caused by the use of insufficiently constrained regular expressions applied to attacker-controlled input: if (issuuid.match(/\d+\/\d+/)) { issuuembed = '#' + issuuid; } else if (issuuid.match(/d=(.)&u=(.)/)) { issuuembed = '?' + issuuid; } These expressions are not anchored and rely on greedy patterns (.). When evaluated against specially crafted input, they may cause excessive backtracking, leading to high CPU consumption and potential denial of service. Impact An attacker able to control the issuuid parameter could exploit this vulnerability to degrade performance or cause temporary service unavailability through CPU exhaustion. No confidentiality or integrity impact was identified. Fix https://github.com/AmauriC/tarteaucitron.js/commit/f0bbdac2fdf3cd24a325fc0928c0d34abf1b7b52 The logic was simplified and…

    Recommended action: Upgrade to 1.29.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  3. Medium, CVSS 4.2npmAmendedPublished

    tarteaucitron.js vulnerable to DOM Clobbering via document.currentScript

    CVE-2025-48939 · GHSA-q43x-79jr-cq98

    Affected
    • npm tarteaucitronjs < 1.22.0
    Fixed in
    1.22.0· Vendor fix available
    Issue
    A vulnerability was identified in tarteaucitron.js where document.currentScript was accessed without verifying that it referenced an actual <script element. If an attacker injected an HTML element such as: it could clobber the document.currentScript property. This causes the script to resolve incorrectly to an <img element instead of the <script tag, leading to unexpected behavior or failure to load the script path correctly. This issue arises because in some browser environments, named DOM elements (e.g., name="currentScript") become properties on the global document object. Impact An attacker with control over the HTML could exploit this to change the CDN domain of tarteaucitron. Fix https://github.com/AmauriC/tarteaucitron.js/commit/230a3b69d363837acfa895823d841e0608826ba3 The issue was resolved by verifying that document.currentScript is an instance of HTMLScriptElement. If not, the script now falls back safely to the last <script tag on the page.

    Recommended action: Upgrade to 1.22.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  4. Medium, CVSS 4.8npmAmendedPublished

    tarteaucitron.js allows url scheme injection via unfiltered inputs

    CVE-2025-31476 · GHSA-p5g4-v748-6fh8

    Affected
    • npm tarteaucitronjs < 1.20.1
    Fixed in
    1.20.1· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 1.20.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  5. Medium, CVSS 5.5npmAmendedPublished

    tarteaucitron.js allows prototype pollution via custom text injection

    CVE-2025-31475 · GHSA-4hwx-xcc5-2hfc

    Affected
    • npm tarteaucitronjs < 1.20.1
    Fixed in
    1.20.1· Vendor fix available
    Issue
    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 https://github.com/AmauriC/tarteaucitron.js/commit/74c354c413ee3f82dff97a15a0a43942887c2b5b The issue was resolved by ensuring that user-controlled inputs cannot modify JavaScript object prototypes.

    Recommended action: Upgrade to 1.20.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  6. Medium, CVSS 5.5npmAmendedPublished

    tarteaucitron.js allows UI manipulation via unrestricted CSS injection

    CVE-2025-31138 · GHSA-7524-3396-fqv3

    Affected
    • npm tarteaucitronjs < 1.20.1
    Fixed in
    1.20.1· Vendor fix available
    Issue
    A vulnerability was identified in tarteaucitron.js, where user-controlled inputs for element dimensions (width and height) were not properly validated. This allowed an attacker with direct access to the site's source code or a CMS plugin to set values like 100%;height:100%;position:fixed;, potentially covering the entire viewport and facilitating clickjacking attacks. Impact An attacker with high privileges could exploit this vulnerability to: - Overlay malicious UI elements on top of legitimate content, - Trick users into interacting with hidden elements (clickjacking), - Disrupt the intended functionality and accessibility of the website. Fix https://github.com/AmauriC/tarteaucitron.js/commit/25fcf828aaa55306ddc09cfbac9a6f8f126e2d07 The issue was resolved by enforcing strict validation and sanitization of user-provided CSS values to prevent unintended UI manipulation.

    Recommended action: Upgrade to 1.20.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  7. Low, CVSS 2.0npmAmendedPublished

    tarteaucitron Cross-site Scripting (XSS)

    CVE-2025-1467 · GHSA-8wp9-x25p-8794

    Affected
    • npm tarteaucitronjs < 1.17.0
    Fixed in
    1.17.0· Vendor fix available
    Issue
    Versions of the package tarteaucitronjs before 1.17.0 are vulnerable to Cross-site Scripting (XSS) via the getElemWidth() and getElemHeight(). This is related to SNYK-JS-TARTEAUCITRONJS-8366541

    Recommended action: Upgrade to 1.17.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  8. Medium, CVSS 4.6npmAmendedPublished

    tarteaucitron.js vulnerable to Cross-site Scripting

    CVE-2023-3620 · GHSA-f44m-65h3-99vc

    Affected
    • npm tarteaucitronjs < 1.13.1
    Fixed in
    1.13.1· Vendor fix available
    Issue
    Cross-site Scripting (XSS) - Stored in GitHub repository amauric/tarteaucitron.js prior to v1.13.1.

    Recommended action: Upgrade to 1.13.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →