Cyber Resilience

CVE-2025-31138

Amauri Tarteaucitronjs ≤ 1.20.1

Published
07 April 2025
Modified
21 October 2025
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
EPSS Score 0.0025 16th percentile
Risk Priority 36 floored blend · peak EPSS

Summary

CVE-2025-31138 is a medium-severity Improper Restriction of Rendered UI Layers or Frames (CWE-1021) vulnerability in Amauri Tarteaucitronjs. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

tarteaucitron.js is a compliant and accessible cookie banner. A vulnerability was identified in tarteaucitron.js prior to 1.20.1, 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…

more

source code or a CMS plugin to set values like 100%;height:100%;position:fixed;, potentially covering the entire viewport and facilitating clickjacking attacks. 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), or disrupt the intended functionality and accessibility of the website. This vulnerability is fixed in 1.20.1.

CWE(s)
CWE-1021

Related Threats

MITRE ATT&CK Enterprise Techniques

T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
attack.mitre.org →
T1056 Input Capture Collection
Adversaries may use methods of capturing user input to obtain credentials or collect information.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-22809Same product: Amauri Tarteaucitronjs
CVE-2025-48939Same product: Amauri Tarteaucitronjs
CVE-2025-31475Same product: Amauri Tarteaucitronjs
CVE-2026-10733Shared CWE-1021
CVE-2023-20913Shared CWE-1021
CVE-2026-12348Shared CWE-1021
CVE-2025-27455Shared CWE-1021
CVE-2024-33377Shared CWE-1021
CVE-2025-14809Shared CWE-1021
CVE-2023-6867Shared CWE-1021

Affected Assets

amauri
tarteaucitronjs
≤ 1.20.1

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require implementing frame-ancestors / X-Frame-Options controls that prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect missing frame protections, but does not itself implement the control.

A.8.23 Web filtering partial match
degrades

Web filtering can block or sandbox untrusted frames, but does not enforce application-level frame-busting or CSP.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate frame-ancestors / X-Frame-Options, directly addressing UI redressing risks.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include isolation of UI layers and proper use of browser security controls.

A.8.28 Secure coding partial match
prevents

Secure coding practices directly require implementation of frame-busting headers or CSP frame-ancestors directives.

References