CVE-2025-48939

mediumpriority · track · 0EPSS 0.002 · 10 %ileEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.20% (10th) EPSS
CVSS 4.2 · medium
Is it mine?
3 products
Check your exposure
Who says so?
4 sources
cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-28

tarteaucitron.js is a compliant and accessible cookie banner. Prior to version 1.22.0, 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, it could clobber the document.currentScript property. This causes the script to resolve incorrectly to an 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 become properties on the global document object. An attacker with control over the HTML could exploit this to change the CDN domain of tarteaucitron. This issue has been patched in version 1.22.0.

01

cvss

Technical severity, 0–10. One row per scoring source.

4.2
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 3.9–4.2

v3.14.2mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:Lsecondary · ENISA EU
v3.14.2mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:Lsecondary · security-advisories@github.comexploitability 1.1 · impact 2.7
v3.14.2mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:Lsecondary · OSV
v3.13.9lowCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:L/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (3)

Products and version ranges known to be affected.

05

advisories (1)

Vendor and ecosystem advisories describing this.

  • GHSA-q43x-79jr-cq98tarteaucitron.js vulnerable to DOM Clobbering via document.currentScript2025-07-03ghsa · osvUS

    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: ``` <img name="currentScript" src="https://malicious.example.com"> ``` 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.

06

also known as (3)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

published 2025-07-03modified 2026-06-17
08

references (7)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan