FortivoiceApplication · Fortinet
CVE-2025-60024
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 · uneditedMultiple Improper Limitations of a Pathname to a Restricted Directory ('Path Traversal') vulnerabilities [CWE-22] vulnerability in Fortinet FortiVoice 7.2.0 through 7.2.2, FortiVoice 7.0.0 through 7.0.7 may allow a privileged authenticated attacker to write arbitrary files via specifically HTTP or HTTPS commands
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 confidenceFortiVoice versions 7.0.0-7.0.7 and 7.2.0-7.2.2 contain multiple path traversal vulnerabilities (CWE-22) that allow a privileged authenticated attacker to write arbitrary files to the filesystem via specially crafted HTTP or HTTPS 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
>= 7.0.0, < 7.0.8>= 7.2.0, < 7.2.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiVoice installed versionAccess the FortiVoice management console and navigate to System > Dashboard > Status, or run 'get system status' via CLI to retrieve the firmware version.Affected if The version falls within 7.0.0-7.0.7 or 7.2.0-7.2.2.
-
Confirm administrative access is enabledCheck System > Administration > Administration Settings in the web UI, or run 'show system admin' via CLI to list administrative accounts and access policies.Affected if Administrative accounts exist and the management interface is accessible.
-
Verify management interface exposureReview network configuration to determine if the HTTPS management port (default 443) is bound to WAN-facing interfaces, or inspect firewall policies allowing external access to FortiVoice management.Affected if The management interface is reachable from untrusted networks.
-
Inspect for unauthorized file modificationsCheck filesystem integrity by reviewing /var/log/ and custom script directories for unexpected files, or run 'diagnose sys fs list' via CLI to enumerate recently created or modified files.Affected if Unexpected files appear in system directories or web root directories.
-
Review administrative logs for suspicious activityExecute 'execute log filter category 1' followed by 'execute log display' to review authentication and administrative action logs, looking for unusual file upload or write operations from privileged accounts.Affected if Logs show file write operations from unexpected IP addresses or at unusual times.
You are affected if FortiVoice version is 7.0.0-7.0.7 or 7.2.0-7.2.2 AND the management interface is accessible to the attacker (either directly or via compromised credentials).
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.0.87.2.3
Upgrade FortiVoice to the latest patched version provided by Fortinet. Additionally, restrict administrative access to trusted IP addresses and implement network segmentation to limit exposure of the management interface.
FortiVoice 7.0.8 or later; FortiVoice 7.2.3 or later
- 1. Backup the current FortiVoice configuration and data before upgrading
- 2. Obtain the fixed firmware version (7.0.8 or later for 7.0.x, 7.2.3 or later for 7.2.x) from the Fortinet support portal at support.fortinet.com
- 3. Upload the firmware upgrade file through the FortiVoice web GUI (System > Firmware) or CLI
- 4. Follow Fortinet's standard firmware upgrade procedure, including any pre-upgrade compatibility checks
- 5. After upgrade, verify the system is operational and confirm the new firmware version is installed
- 6. Test that FortiVoice functionality (call handling, extensions, voicemail) is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortivoice
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60024 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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