dbcve.org
FortivoiceApplication · Fortinet

CVE-2025-64156

HIGH · 7.2 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to after 7.2.1 or later.
See remediation →
78/100
Remediation priority · High
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 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

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 allows authenticated privileged attackers to execute unauthorized code or commands via crafted SQL requests. The flaw exists in the input handling of certain parameters that are directly incorporated into SQL queries without proper sanitization or use of parameterized statements.

MitigationUpdate FortiVoice to a patched version beyond 7.2.2 (or 7.0.8+) as provided by Fortinet's security advisory. As an interim measure, restrict administrative access to trusted IP addresses and monitor for suspicious 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:>= 6.0.0, <= 6.0.12>= 6.4.0, <= 6.4.11>= 7.0.0, <= 7.0.7>= 7.2.0, <= 7.2.1

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Check FortiVoice version
    Log into the FortiVoice CLI and run the command to display system status, or access the web interface System > Settings to view the firmware version. Compare your version against the affected ranges: 6.0.0 through 6.0.12, 6.4.0 through 6.4.11, 7.0.0 through 7.0.7, and 7.2.0 through 7.2.1
    Affected if Your installed version falls within any of the listed version ranges
  2. Verify administrative interface exposure
    Inspect the FortiVoice network configuration to determine if the web-based administrative interface is reachable from external or untrusted networks. Check interface bindings and firewall policies that permit access to the management ports
    Affected if The administrative web interface is accessible from untrusted networks or IP addresses beyond your internal trusted range
  3. Confirm privileged access requirements
    Determine if the affected SQL injection endpoint is accessible to any administrative role. In FortiVoice, verify which user roles have access to the specific parameters involved in SQL query handling
    Affected if Your administrative users with access to the vulnerable parameter input are not strictly limited to fully trusted personnel

You are affected if your FortiVoice version falls within the affected ranges AND the administrative interface or vulnerable parameter inputs are accessible to untrusted authenticated users.

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 a release after 7.2.1
Interim mitigation

Update FortiVoice to a patched version beyond 7.2.2 (or 7.0.8+) as provided by Fortinet's security advisory. As an interim measure, restrict administrative access to trusted IP addresses and monitor for suspicious SQL-like patterns in requests.

Recommended fix High confidence

FortiVoice 6.0.13+, 6.4.12+, 7.0.8+, or 7.2.2+ (latest stable release recommended: 7.4.0 or later)

  1. 1. Identify the currently installed FortiVoice version via the web UI (System > Dashboard > Status) or CLI: 'get system status'
  2. 2. Based on your current major version branch, plan upgrade path: FortiVoice 6.0.x -> 6.0.13 or later; 6.4.x -> 6.4.12 or later; 7.0.x -> 7.0.8 or later; 7.2.x -> 7.2.2 or later
  3. 3. Download the appropriate firmware upgrade from Fortinet Customer Support Portal (https://support.fortinet.com) or FortiGuard
  4. 4. Back up the FortiVoice configuration via CLI: 'execute backup config tftp <config-file> <tftp-server-ip>' or via web UI
  5. 5. Upgrade firmware via web UI (System > Firmware > Upgrade) or CLI: 'execute system firmware upgrade <image-file> tftp <tftp-server-ip>'
  6. 6. After reboot, verify upgrade: 'get system status' and confirm version is beyond vulnerable range
  7. 7. Verify the SQL injection is no longer present by confirming the patched version is running
Caveat Review Fortinet release notes for the target version for any configuration or feature changes; test upgrade in staging environment before production deployment

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

Fix this in Fortivoice Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64156 — 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-64156 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