CVE-2025-6725 json
Cross-Site Scripting (XSS) in PdfViewer
published 2025-07-02 16 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-19729
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
In the PdfViewer component, a Cross-Site Scripting (XSS) vulnerability is possible if a specially-crafted document has already been loaded and the user engages with a tool that requires the DOM to be re-rendered.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 16 mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Progress Software Kendo UI for jQuery
- Progress Software Kendo UI for Angular
- Progress Software KendoReact
- Progress Software Telerik UI for ASP.NET MVC
- Progress Software Telerik UI for ASP.NET Core
- Progress Software Telerik UI for Blazor
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
- telerik.com /blazor-ui/documentation/knowledge-base/pdfviewer-xss-vulnerability-cve-2025-6725
- telerik.com /aspnet-core-ui/documentation/knowledge-base/kb-security-pdfviewer-xss-cve-2025-6725
- telerik.com /aspnet-mvc/documentation/knowledge-base/kb-security-pdfviewer-xss-cve-2025-6725
- telerik.com /kendo-jquery-ui/documentation/knowledge-base/kb-security-pdfviewer-xss-cve-2025-6725
- telerik.com /kendo-angular-ui/components/knowledge-base/kb-security-pdfviewer-xss-cve-2025-6725
- telerik.com /kendo-react-ui/components/knowledge-base/kb-security-pdfviewer-xss-cve-2025-6725
Sources
- CVE List CVE-2025-6725
- NVD CVE-2025-6725
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.