CVE-2025-1461VulnerabilityPublished 28 May 2025Updated 29 May 2025

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

Affects VuetifySource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.6Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% 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:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: None: The vulnerable system can be exploited without any interaction from any user.
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 28 May 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 2026-10-25.

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

European organizations should undertake a thorough inventory of web applications using Vuetify 2.x and specifically the 'VCalendar' component. Immediate mitigation steps include: 1) Upgrading to Vuetify 3.x or later, which is actively maintained and not affected by this vulnerability. If upgrade is not feasible, consider refactoring to remove or replace the vulnerable component. 2) Implement strict input validation and output encoding on any user-controllable inputs that influence the 'eventMoreText' property to prevent injection of malicious HTML. 3) Employ Content Security Policy (CSP) headers to restrict script execution sources and reduce the impact of potential XSS attacks. 4) Use web application firewalls (WAFs) with rules targeting XSS patterns to detect and block exploit attempts. 5) Conduct security testing, including automated scanning and manual code review, focusing on UI components rendering dynamic content. 6) Educate developers on secure coding practices related to UI frameworks and translation mechanisms. These targeted actions go beyond generic advice by addressing the specific nature of the vulnerability and the challenges posed by the EOL status of the affected Vuetify versions.

Description

Improper neutralization of the value of the 'eventMoreText' property of the 'VCalendar' 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 default Vuetify translator will return the translation key as the translation, if it can't find an actual translation. 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 poses a risk primarily to web applications built with Vuetify 2.x that incorporate the vulnerable 'VCalendar' component. Successful exploitation could lead to client-side script execution, enabling attackers to steal session cookies, perform actions on behalf of users, or deliver malicious payloads. This can compromise user data confidentiality and integrity, damage organizational reputation, and potentially lead to regulatory non-compliance under GDPR if personal data is exposed. The impact is heightened for organizations in sectors with high web application usage such as e-commerce, finance, healthcare, and government services. Since the vulnerability is in a UI framework, it may be present in multiple internal and customer-facing applications, increasing the attack surface. The lack of patches due to the EOL status of Vuetify 2.x complicates mitigation, potentially prolonging exposure. However, the medium severity and high attack complexity somewhat limit the immediacy of risk, but organizations should still prioritize remediation to prevent exploitation.

Summary

CVE-2025-1461 is a medium severity Cross-Site Scripting (XSS) vulnerability identified in the Vuetify UI framework, specifically affecting the 'VCalendar' component's 'eventMoreText' property. Vuetify versions from 2.0.0 up to but not including 3.0.0 are impacted. The root cause lies in improper neutralization of input during web page generation (CWE-79). When the default Vuetify translator cannot find a translation key, it returns the key itself as the translation string. This behavior allows unsanitized HTML content to be injected into the page via the 'eventMoreText' property, enabling an attacker to execute arbitrary scripts in the context of the victim's browser. Since version 2.x of Vuetify is End-of-Life and no longer maintained, no official patches are available to remediate this issue. The vulnerability does not require user interaction or authentication but has a high attack complexity, as exploitation depends on the attacker’s ability to control or influence the 'eventMoreText' property value. The CVSS v3.1 base score is 5.6, reflecting a medium severity with limited confidentiality, integrity, and availability impacts. No known exploits are currently reported in the wild. This vulnerability primarily affects web applications using the vulnerable Vuetify versions, potentially exposing users to session hijacking, credential theft, or other malicious activities facilitated by XSS attacks.

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 7 Jul 2025, 04:41 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats