Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Authenticated SQL Injection in Fortinet FortiVoice

IdentifiersCVE-2025-58692CWE-89· Improper Neutralization of Special…

CVE-2025-58692 is an authenticated SQL injection vulnerability in Fortinet FortiVoice affecting versions 7.2.0 through 7.2.2 and 7.0.0 through 7.0.7. The flaw is caused by insufficient input sanitization in certain HTTP or HTTPS endpoints exposed by the FortiVoice web interface or API, where attacker-controlled input is reportedly concatenated into backend SQL queries without adequate parameterization or escaping. An authenticated attacker can send specifically crafted requests to inject malicious SQL statements, causing the backend database to execute unauthorized queries or database-level commands. Publicly available content does not identify the exact vulnerable endpoint or function, but it consistently describes the issue as a CWE-89 SQL injection in FortiVoice management functionality.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an authenticated attacker to execute unauthorized SQL queries against the FortiVoice backend database and potentially issue unauthorized commands, depending on the privileges available to the application and database context. Likely impacts include disclosure of sensitive data stored in the database, modification or deletion of records such as call-related data, manipulation of application state, and privilege escalation within the application. If the database environment or integrated command-execution features permit it, exploitation may also lead to unauthorized code or command execution.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of the FortiVoice web interface and API to only trusted administrative networks, restrict access over HTTP/HTTPS with network ACLs or segmentation, minimize the number of accounts that can authenticate to the management interface, and monitor for anomalous crafted requests and unexpected database activity. Because exploitation requires authentication, enforcing strong credential hygiene, MFA where supported, and rapid revocation of unnecessary or stale accounts can reduce risk, but these measures do not eliminate the underlying vulnerability.

Remediation

Patch, then assume compromise.

Upgrade FortiVoice to a fixed release. The provided content states that Fortinet resolved this issue in FortiVoice 7.2.3 and later, and references PSIRT advisory FG-IR-25-666 and the 7.2.3 release notes as the vendor remediation source. Organizations running affected 7.2.x or 7.0.x builds should apply the vendor-provided update on an expedited basis and validate that all FortiVoice instances have been moved off vulnerable versions.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetFortivoiceapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.