FortiManager and FortiAnalyzer

CVE-2024-33502: Path traversal in FortiManager, FortiAnalyzer

An improper limitation of a pathname to a restricted directory ('path traversal') in Fortinet FortiManager, FortiAnalyzer versions 7.4.0 through 7.4.2 and 7.2.0 through 7.2.5 and 7.0.0 through 7.0.12 and 6.4.0 through 6.4.14 and 6.2.0 through 6.2.12 and 6.0.0 through 6.0.12 allows attacker to execute unauthorized code or commands via crafted HTTP or HTTPs requests.

Published

ExploitedNot in CISA KEV
Ransomware useNot reportedPer CISA
SeverityMEDIUMCVSS 3.1 6.4
EPSS1.3%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
FortiManager 7.4.0 to 7.4.27.4.3 or later
FortiManager 7.2.0 to 7.2.57.2.6 or later
FortiManager 7.0.0 to 7.0.13Upgrade past 7.0.13; see the advisory
FortiManager 6.4.0 to 6.4.15Upgrade past 6.4.15; see the advisory
FortiManager 6.2.0 to 6.2.13Upgrade past 6.2.13; see the advisory
FortiManager 6.0.0 to 6.0.12Upgrade past 6.0.12; see the advisory
FortiAnalyzer 7.4.0 to 7.4.27.4.3 or later
FortiAnalyzer 7.2.0 to 7.2.57.2.6 or later
FortiAnalyzer 7.0.0 to 7.0.13Upgrade past 7.0.13; see the advisory
FortiAnalyzer 6.4.0 to 6.4.15Upgrade past 6.4.15; see the advisory
FortiAnalyzer 6.2.0 to 6.2.13Upgrade past 6.2.13; see the advisory
FortiAnalyzer 6.0.0 to 6.0.12Upgrade past 6.0.12; see the advisory

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

What it is

An improper limitation of a pathname to a restricted directory ('path traversal') in Fortinet FortiManager, FortiAnalyzer versions 7.4.0 through 7.4.2 and 7.2.0 through 7.2.5 and 7.0.0 through 7.0.12 and 6.4.0 through 6.4.14 and 6.2.0 through 6.2.12 and 6.0.0 through 6.0.12 allows attacker to execute unauthorized code or commands via crafted HTTP or HTTPs requests.

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.