CVE-2025-1461 is a cross-site scripting vulnerability in the VCalendar component of Vuetify 2.x. The issue stems from improper neutralization of the value of the eventMoreText property, allowing unsanitized HTML to be inserted into the rendered page. According to the provided description, the vulnerable behavior is tied to the default Vuetify translator, which returns the translation key itself when no matching translation is found. If attacker-controlled input is supplied in this context, that value can be rendered as HTML rather than safely escaped, resulting in XSS. The issue affects Vuetify versions greater than or equal to 2.0.0 and less than 3.0.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (POC) for CVE-2025-1461, a Cross-Site Scripting (XSS) vulnerability in the Vuetify VCalendar component (versions >=2.0.0 and <3.0.0). The exploit demonstrates that the 'eventMoreText' prop is not sanitized and is directly assigned to innerHTML, allowing an attacker to inject arbitrary HTML/JavaScript. The repository is structured as a minimal Vue.js application using Vuetify 2.7.2, with the main exploit logic in 'src/components/Reproduction.vue'. This file shows two calendar implementations: one with a malicious 'eventMoreText' containing an onclick handler that triggers an alert (demonstrating XSS), and one with the default value for comparison. The application can be run locally via 'npm run dev' and accessed at 'http://localhost:3000'. The repository includes supporting files for Vue, Vuetify, and Vite configuration, but the core exploit is the injection of a crafted HTML string into the VCalendar component. No external network targets are involved; the attack vector is browser-based XSS via a local or test instance of the vulnerable component.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.