dbcve.org
FortivoiceApplication · Fortinet

CVE-2025-47856

HIGH · 7.2 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 6.4.11 / 7.0.7 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
Two improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerabilities [CWE-78] in Fortinet FortiVoice version 7.2.0, 7.0.0 through 7.0.6 and before 6.4.10 allows a privileged attacker to execute arbitrary code or commands via crafted HTTP/HTTPS or CLI 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

OS command injection vulnerability in FortiVoice allows authenticated privileged attackers to execute arbitrary commands via specially crafted HTTP/HTTPS or CLI requests. The vulnerability affects versions 7.2.0, 7.0.0 through 7.0.6, and versions before 6.4.10. This is a CWE-78 (OS Command Injection) flaw where improper neutralization of special elements in OS commands occurs.

MitigationApply the vendor-supplied security patch from Fortinet for FortiVoice. Since this requires privileged access, enforce least-privilege principles for administrative accounts and monitor for anomalous administrative activities or suspicious CLI/HTTP request patterns.

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.4.0, < 6.4.11>= 7.0.0, < 7.0.7= 7.2.0

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. Identify FortiVoice version
    Access the FortiVoice web UI or CLI and navigate to the system status or version information page. In the CLI, run 'get system status' or 'fwm -d status' to retrieve the firmware version.
    Affected if The installed version is 7.2.0, or 7.0.0 through 7.0.6, or 6.4.0 through 6.4.10 (i.e., falls within >= 6.4.0, < 6.4.11; >= 7.0.0, < 7.0.7; or equals 7.2.0).
  2. Confirm HTTP/HTTPS management interface is enabled
    Check the FortiVoice network configuration via the web UI under System > Network > Interface, or run 'show system interface' in the CLI to see which interfaces have management access enabled.
    Affected if HTTP or HTTPS management is enabled on any accessible network interface, allowing remote attackers to send specially crafted requests.
  3. Verify CLI access is available
    Check if SSH or console access is configured. In the web UI, go to System > Admin > Administrators to review access methods, or run 'show system interface' to check for SSH-enabled interfaces.
    Affected if SSH or console access is permitted, as the vulnerability can be exploited via CLI requests.
  4. Review administrative accounts and privileges
    In the FortiVoice web UI, navigate to System > Admin > Administrators to list all accounts. In the CLI, run 'get system admin' to see administrator accounts and their profiles.
    Affected if Multiple privileged administrator accounts exist or accounts with elevated permissions beyond least-privilege principles are present, increasing exploitation risk.
  5. Inspect system logs for suspicious command activity
    In the FortiVoice web UI, go to Log & Report > Event Log > System Events. Look for entries involving CLI commands, particularly those with unusual syntax or originating from unexpected sources.
    Affected if Logs contain anomalous CLI commands, unexpected execution patterns, or entries indicating privilege escalation attempts.

You are affected if your FortiVoice version falls within 6.4.0 to 6.4.10, 7.0.0 to 7.0.6, or equals 7.2.0, and the management interface (HTTP/HTTPS or CLI) is accessible to authenticated privileged 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 6.4.11 / 7.0.7 or later
Fixed in 6.4.117.0.7
Interim mitigation

Apply the vendor-supplied security patch from Fortinet for FortiVoice. Since this requires privileged access, enforce least-privilege principles for administrative accounts and monitor for anomalous administrative activities or suspicious CLI/HTTP request patterns.

Recommended fix High confidence

FortiVoice 6.4.x -> 6.4.11+; FortiVoice 7.0.x -> 7.0.7+; FortiVoice 7.2.0 -> 7.2.1+

  1. 1. Identify the currently installed FortiVoice version by checking the system information in the FortiVoice admin GUI or via CLI command 'get system status'
  2. 2. Determine which version branch you are currently running (6.4.x, 7.0.x, or 7.2.0)
  3. 3. For FortiVoice 6.4.x (versions 6.4.0 through 6.4.10): Plan upgrade to version 6.4.11 or later
  4. 4. For FortiVoice 7.0.x (versions 7.0.0 through 7.0.6): Plan upgrade to version 7.0.7 or later
  5. 5. For FortiVoice 7.2.0: Plan upgrade to version 7.2.1 or later (if available) or the next stable release in the 7.2 branch
  6. 6. Before upgrading, backup the FortiVoice configuration via GUI (System > Configuration > Backup) or CLI command 'execute backup config'
  7. 7. Review Fortinet's upgrade documentation and release notes for any specific migration requirements
  8. 8. Perform the upgrade via FortiVoice GUI (System > Firmware) or CLI command 'execute firmware upgrade', or upload the firmware file manually
Caveat Review release notes for any configuration changes or feature modifications between your current version and the target version before upgrading

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

Fix this in Fortivoice Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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