dbcve.org
FortivoiceApplication · Fortinet

CVE-2025-58692

HIGH · 8.8 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 7.0.8 / 7.2.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An improper neutralization of special elements used in an SQL Command ("SQL Injection") vulnerability [CWE-89] vulnerability in Fortinet FortiVoice 7.2.0 through 7.2.2, FortiVoice 7.0.0 through 7.0.7 allows an authenticated attacker to execute unauthorized code or commands via specifically crafted HTTP or HTTPS requests.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in FortiVoice versions 7.0.0-7.0.7 and 7.2.0-7.2.2 allows authenticated attackers to execute unauthorized code or commands via specially crafted HTTP/HTTPS requests. The vulnerability stems from improper neutralization of special elements in SQL commands (CWE-89).

MitigationUpgrade FortiVoice to a patched version beyond 7.0.7 and 7.2.2 as specified in Fortinet's security advisory. Until patching is possible, restrict access to the management interface to trusted users only and monitor for anomalous SQL-like patterns in requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortivoiceApplication
Affected:>= 7.0.0, < 7.0.8>= 7.2.0, < 7.2.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine FortiVoice installed version
    Log into the FortiVoice management console or use CLI command 'get system status' to retrieve the firmware version
    Affected if The version displayed is 7.0.0 through 7.0.7 or 7.2.0 through 7.2.2 (versions below 7.0.8 or 7.2.3)
  2. Confirm management interface accessibility
    Verify whether the FortiVoice web UI (HTTPS port) or CLI is reachable from network segments containing untrusted users
    Affected if The management interface is exposed to networks with untrusted or unknown users
  3. Identify authentication method in use
    Review user accounts configured in FortiVoice under System > Administrator to determine if local database authentication is enabled
    Affected if Local database authentication is in use and any admin accounts could be compromised
  4. Inspect logs for suspicious SQL patterns
    Check FortiVoice logs under Log & Report > Event Log for entries containing SQL keywords (SELECT, UNION, DROP) or unusual database query errors
    Affected if Logs show SQL injection attempts or unexpected database error messages

A FortiVoice system is affected if it runs version 7.0.0-7.0.7 or 7.2.0-7.2.2 and has its management interface accessible to authenticated attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.8 / 7.2.3 or later
Fixed in 7.0.87.2.3
Interim mitigation

Upgrade FortiVoice to a patched version beyond 7.0.7 and 7.2.2 as specified in Fortinet's security advisory. Until patching is possible, restrict access to the management interface to trusted users only and monitor for anomalous SQL-like patterns in requests.

Recommended fix High confidence

FortiVoice 7.0.8 or FortiVoice 7.2.3 (depending on your current branch)

  1. 1. Back up the current FortiVoice configuration before proceeding with the upgrade.
  2. 2. Obtain the fixed version from Fortinet's official support portal: FortiVoice 7.0.8 for 7.0.x branches, or FortiVoice 7.2.3 for 7.2.x branches.
  3. 3. Upload the firmware image to the FortiVoice device via the web UI or CLI.
  4. 4. Initiate the firmware upgrade and allow the process to complete without interruption.
  5. 5. After reboot, verify the system is running the fixed version (7.0.8 or 7.2.3).
  6. 6. Confirm the SQL injection vulnerability is resolved by testing with the fixed release.
Caveat Upgrading within the same major.minor version branch (e.g., 7.0.x to 7.0.8) typically has minimal breaking changes; review Fortinet release notes for any configuration or feature adjustments.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortivoice Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58692 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58692 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data