dbcve.org
FortivoiceApplication · Fortinet

CVE-2025-58693

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 7.0.8 / 7.2.3 or later.
See remediation →
71/100
Remediation priority · Elevated
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 limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiVoice 7.2.0 through 7.2.2, FortiVoice 7.0.0 through 7.0.7 allows a privileged attacker to delete files from the underlying filesystem via 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

Path traversal vulnerability in FortiVoice versions 7.2.0 through 7.2.2 and 7.0.0 through 7.0.7 allows an authenticated privileged attacker to delete arbitrary files from the underlying filesystem via specially crafted HTTP or HTTPS requests.

MitigationUpgrade FortiVoice to the vendor-patched version (7.2.3 or later for the 7.2.x branch, 7.0.8 or later for the 7.0.x branch) to remediate this vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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
    Log into the FortiVoice web interface or CLI and navigate to System > Dashboard > Status or use 'get system status' command in CLI to view the firmware version
    Affected if Version is 7.0.0 through 7.0.7 or 7.2.0 through 7.2.2 (version falls within >=7.0.0,<7.0.8 or >=7.2.0,<7.2.3)
  2. Verify web interface accessibility
    Confirm that FortiVoice HTTP/HTTPS service is enabled and reachable by attempting to access the login page via browser or checking listening ports (typically 80/443 or 8443)
    Affected if Web interface is enabled and exposed on network (this is the attack vector required for exploitation)
  3. Confirm privileged user configuration
    Check if privileged administrative accounts exist in FortiVoice under User & Authentication > User Group or via 'show system admin' command in CLI
    Affected if Privileged administrator accounts are configured (exploitation requires an authenticated privileged attacker)

Environment is affected if FortiVoice version is 7.0.0-7.0.7 or 7.2.0-7.2.2 AND the web interface is accessible AND privileged users can authenticate.

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 the vendor-patched version (7.2.3 or later for the 7.2.x branch, 7.0.8 or later for the 7.0.x branch) to remediate this vulnerability.

Recommended fix High confidence

FortiVoice 7.0.8 (for 7.0.x users) or FortiVoice 7.2.3+ (for 7.2.x users)

  1. Identify the currently installed FortiVoice version (7.0.x or 7.2.x branch)
  2. Download the appropriate fixed version from Fortinet's support portal: 7.0.8 for the 7.0.x branch or 7.2.3+ for the 7.2.x branch
  3. Review Fortinet's release notes for the target version to understand any configuration or behavioral changes
  4. Schedule a maintenance window and back up the current FortiVoice configuration
  5. Upgrade FortiVoice to the fixed version (7.0.8 or 7.2.3 or later)
  6. Verify the upgrade completed successfully and confirm the new version number
  7. Test that FortiVoice services are functioning normally after the upgrade
Caveat Refer to Fortinet release notes for the target version; minor version upgrades typically have minimal breaking changes but review release notes for any configuration adjustments required

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 / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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