CVE-2025-8082VulnerabilityPublished 12 Dec 2025

CVE-2025-8082: Vuetify · XSS or 'Cross-site Scripting'

Affects VuetifySource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.0.0 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Vuetify to 3.0.0.

Affected software

Product	Affected	Fixed in
npmvuetify`pkg:npm/vuetify`Other threats	Affected >=2.0.0 <3.0.0	Fixed in 3.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since Vuetify 2.x is end-of-life and no official patches will be released, the primary mitigation is to upgrade affected applications to Vuetify 3, which addresses this vulnerability. If immediate upgrade is not feasible, organizations should implement strict input validation and sanitization on any user-supplied data passed to the 'title-date-format' property or avoid using custom functions that generate HTML for this property. Employing a robust Content Security Policy (CSP) that restricts script execution and disallows inline scripts can reduce the impact of XSS attacks. Additionally, web application firewalls (WAFs) can be configured to detect and block malicious payloads targeting this vulnerability. Regular security testing, including automated scanning and manual code review focusing on the usage of VDatePicker and its properties, is recommended. Educating developers about safe usage patterns and avoiding direct innerHTML assignments without sanitization is critical. Monitoring for suspicious activity and user reports of unusual behavior can help detect exploitation attempts.

Description

Improper neutralization of the title date in the 'VDatePicker' component in Vuetify, allows unsanitized HTML to be inserted into the page. This can lead to a Cross-Site Scripting (XSS) https://owasp.org/www-community/attacks/xss attack. The vulnerability occurs because the 'title-date-format' property of the 'VDatePicker' can accept a user created function and assign its output to the 'innerHTML' property of the title element without sanitization. This issue affects Vuetify versions greater than or equal to 2.0.0 and less than 3.0.0. Note: Version 2.x of Vuetify is End-of-Life and will not receive any updates to address this issue. For more information see here https://v2.vuetifyjs.com/en/about/eol/ .

Impact

For European organizations, this vulnerability can lead to unauthorized script execution in users' browsers, resulting in session hijacking, data theft, or defacement of web applications. Although the confidentiality, integrity, and availability impacts are rated low, the exploitation can facilitate phishing attacks or further compromise user accounts. Organizations relying on Vuetify 2.x in customer-facing or internal web applications are at risk, especially if these applications handle sensitive data or authentication tokens. The lack of vendor patches due to end-of-life status increases the risk exposure. Additionally, regulatory frameworks such as GDPR require protection of user data, and exploitation of this vulnerability could lead to data breaches and associated compliance penalties. The threat is particularly relevant for sectors with high web application usage, including finance, e-commerce, and public services across Europe.

Summary

CVE-2025-8082 is a Cross-Site Scripting (XSS) vulnerability classified under CWE-79, affecting Vuetify versions from 2.0.0 up to but not including 3.0.0. The vulnerability stems from the 'VDatePicker' component's 'title-date-format' property, which accepts a user-defined function whose output is directly assigned to the innerHTML of the title element without proper sanitization. This improper neutralization allows an attacker to inject malicious HTML or JavaScript code into the web page, potentially executing arbitrary scripts in the context of the victim's browser. The vulnerability requires no authentication but does require user interaction, such as clicking a crafted link or visiting a malicious page. The CVSS v3.1 base score is 6.3 (medium), reflecting network attack vector, low attack complexity, no privileges required, user interaction required, and impacts on confidentiality, integrity, and availability at a low level. Notably, Vuetify 2.x is end-of-life and will not receive patches, meaning vulnerable applications must either upgrade to Vuetify 3 or apply alternative mitigations. No public exploits are known at this time, but the vulnerability poses a risk to any web application using the affected Vuetify versions, especially those exposing the VDatePicker component with user-controllable 'title-date-format' functions.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Dec 2025, 19:01 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats