CVE-2025-60950: 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 20% 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 30 Oct 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-60950, organizations should implement the following specific measures: 1) Immediately restrict or disable SVG file uploads in AIxBlock's Data Preparation function until a patch is available. 2) Employ strict input validation and sanitization on all uploaded files, especially SVGs, to remove or neutralize embedded scripts or malicious content. 3) Use file type verification beyond file extensions, such as MIME type checks and content inspection, to prevent disguised malicious files. 4) Implement application-layer security controls like Content Security Policy (CSP) to limit script execution from uploaded files. 5) Monitor logs and network traffic for unusual file upload activities or execution attempts related to AIxBlock. 6) Educate users about the risks of uploading untrusted files and enforce policies to limit uploads to trusted sources. 7) Deploy endpoint protection and behavior-based detection to identify and block suspicious code execution. 8) Engage with AIxBlock vendors or maintainers to obtain timely patches or updates addressing this vulnerability. 9) Consider isolating AIxBlock processing environments to contain potential exploitation impact. 10) Regularly review and update incident response plans to include scenarios involving arbitrary code execution via file uploads.
Description
An arbitrary file upload vulnerability in the Data Preparation function of AIxBlock commit f60975 allows attackers to execute arbitrary code via a crafted SVG file.