CVE-2025-64156: Fortinet FortiVoice · Execute unauthorized code or commands
Affects Fortinet FortiVoiceSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:U/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 9 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Fortinet FortiVoice | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-64156, organizations should implement the following specific measures: 1) Immediately review and restrict administrative access to FortiVoice systems, enforcing the principle of least privilege and strong authentication mechanisms such as multi-factor authentication (MFA) for all privileged accounts. 2) Monitor Fortinet’s official channels for patches or security updates addressing this vulnerability and apply them promptly upon release. 3) Conduct thorough audits of FortiVoice logs and configurations to detect any anomalous or unauthorized activities indicative of exploitation attempts. 4) Employ network segmentation to isolate FortiVoice systems from general user networks, limiting exposure to potential attackers. 5) Implement Web Application Firewalls (WAFs) or intrusion prevention systems (IPS) with custom rules to detect and block SQL injection patterns targeting FortiVoice interfaces. 6) Regularly update and patch all related infrastructure components to reduce the risk of chained exploits. 7) Educate administrators on secure handling of privileged credentials and the risks associated with SQL injection vulnerabilities. 8) Consider deploying endpoint detection and response (EDR) solutions on management workstations to identify suspicious activities related to FortiVoice administration. These targeted actions go beyond generic advice and focus on reducing the attack surface and improving detection capabilities specific to this vulnerability.
Description
An improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fortinet FortiVoice 7.2.0 through 7.2.2, FortiVoice 7.0.0 through 7.0.7, FortiVoice 6.4 all versions, FortiVoice 6.0 all versions may allow an authenticated privileged attacker to execute unauthorized code or commands via crafted requests