CVE-2025-63872: n/a
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 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 2026-10-25.
What to do
AI-suggested
To mitigate CVE-2025-63872, organizations should implement multiple layers of defense: 1) Apply strict input validation and sanitization on all model-generated SVG content to ensure no executable scripts can be injected. 2) Employ Content Security Policy (CSP) headers to restrict the execution of inline scripts and limit the sources of executable code in browsers. 3) Disable or restrict SVG rendering in contexts where it is not essential, or use safer rendering libraries that do not allow script execution. 4) Monitor web application logs and user activity for signs of suspicious SVG content or unusual script execution. 5) Educate users about the risks of interacting with untrusted SVG content and encourage cautious behavior. 6) Stay alert for official patches or updates from DeepSeek and apply them promptly once available. 7) Consider network-level controls such as web application firewalls (WAFs) configured to detect and block XSS payloads targeting SVG content. These measures collectively reduce the attack surface and limit the potential for exploitation.
Description
DeepSeek V3.2 has a Cross Site Scripting (XSS) vulnerability, which allows JavaScript execution through model-generated SVG content.