# CVE-2025-1461: Vuetify XSS through 'eventMoreText' prop of VCalendar

> Attackers can inject malicious scripts via the eventMoreText prop in Vuetify's VCalendar component, affecting the end-of-life version 2.x.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2025
- **Updated:** 29 May 2025
- **Also known as:** GHSA-vr9v-xw27-65fc

## What is CVE-2025-1461?

CVE-2025-1461 is a medium-severity cross-site scripting vulnerability in Vuetify, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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/ .

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-1461?


## How do I fix CVE-2025-1461?

Product is end of life, replace it.

## Is CVE-2025-1461 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1461 exists.

Public exploit code:

- https://github.com/neverendingsupport/nes-vuetify-cve-2025-1461 (github_poc): https://github.com/neverendingsupport/nes-vuetify-cve-2025-1461

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1461 and fix it if it is affected.

What it is: CVE-2025-1461 is a medium-severity cross-site scripting vulnerability in Vuetify, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1461 exists.

Affected product: Vuetify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1461/ (Markdown: https://insights.sbomify.com/CVE-2025-1461/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1461
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1461
- OSV: https://osv.dev/vulnerability/CVE-2025-1461

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1461/
Summaries are generated and may contain mistakes; the official description above is the record.