FortiWeb

CVE-2024-48885: Path traversal in FortiVoice, FortiRecorder and others

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiRecorder 7.2.0 through 7.2.1, FortiRecorder 7.0.0 through 7.0.4, FortiVoice 7.0.0 through 7.0.4, FortiVoice 6.4.0 through 6.4.9, FortiVoice 6.0 all versions, FortiWeb 7.6.0, FortiWeb 7.4.0 through 7.4.4, FortiWeb 7.2 all versions, FortiWeb 7.0 all versions, FortiWeb 6.4 all versions allows attacker to escalate privilege via specially crafted packets.

Published

ExploitedNot in CISA KEV
Ransomware useNot reportedPer CISA
SeverityMEDIUMCVSS 3.1 5.2
EPSS0.79%Chance of exploitation in 30 days
Public exploitNot tracked
FixAvailable

Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.

Affected and fixed versions

Product / branchFixed in
FortiVoice 7.0.0 to 7.0.47.0.5 or later
FortiVoice 6.4.0 to 6.4.96.4.10 or later
FortiVoice 6.0.0 to 6.0.12Upgrade past 6.0.12; see the advisory
FortiRecorder 7.2.0 to 7.2.17.2.2 or later
FortiRecorder 7.0.0 to 7.0.47.0.5 or later
FortiWeb 7.67.6.1 or later
FortiWeb 7.4.0 to 7.4.47.4.5 or later
FortiWeb 7.2.0 to 7.2.12Upgrade past 7.2.12; see the advisory
FortiWeb 7.0.0 to 7.0.12Upgrade past 7.0.12; see the advisory
FortiWeb 6.4.0 to 6.4.3Upgrade past 6.4.3; see the advisory

Always confirm against the vendor advisory, which lists every fixed hotfix.

What it is

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiRecorder 7.2.0 through 7.2.1, FortiRecorder 7.0.0 through 7.0.4, FortiVoice 7.0.0 through 7.0.4, FortiVoice 6.4.0 through 6.4.9, FortiVoice 6.0 all versions, FortiWeb 7.6.0, FortiWeb 7.4.0 through 7.4.4, FortiWeb 7.2 all versions, FortiWeb 7.0 all versions, FortiWeb 6.4 all versions allows attacker to escalate privilege via specially crafted packets.

Sources

KEV status, EPSS score and vendor data refreshed automatically, last on 10 Oct 2026.

Get alerts

A notification when we publish a new analysis or a covered vendor gets a new actively exploited CVE. No account, no email.