CVE-2024-26013

HIGH
7.5
CVSS Score
Published: April 8, 2025 at 02:03 PM UTC
Updated: June 17, 2026 at 07:16 AM UTC
6 products affected across 1 vendorFortiOSFortiProxyFortiWeb

Using FortiProxy by Fortinet?

Get instant alerts when new vulnerabilities affect FortiProxy - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

A improper restriction of communication channel to intended endpoints vulnerability [CWE-923] in Fortinet FortiOS version 7.4.0 through 7.4.4, 7.2.0 through 7.2.8, 7.0.0 through 7.0.15, 6.4.0 through 6.4.15 and before 6.2.16, Fortinet FortiProxy version 7.4.0 through 7.4.2, 7.2.0 through 7.2.9 and before 7.0.15, Fortinet FortiManager version 7.4.0 through 7.4.2, 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, 6.4.0 through 6.4.14 and before 6.2.13, Fortinet FortiAnalyzer version 7.4.0 through 7.4.2, 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, 6.4.0 through 6.4.14 and before 6.2.13, Fortinet FortiVoice version 7.0.0 through 7.0.2 before 6.4.8 and Fortinet FortiWeb before 7.4.2 may allow an unauthenticated attacker in a man-in-the-middle position to impersonate the management device (FortiCloud server or/and in certain conditions, FortiManager), via intercepting the FGFM authentication request between the management device and the managed device

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.2.0 ≤ v < 6.2.146.4.0 ≤ v < 6.4.157.0.0 ≤ v < 7.0.127.2.0 ≤ v < 7.2.57.4.0 ≤ v < 7.4.3
Affected range stops below 6.2.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.2.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.4.3, so it looks safe — our inference, not a vendor statement
6.2.0 ≤ v ≤ 6.2.136.2.0 ≤ v < 6.2.146.4.0 ≤ v ≤ 6.4.146.4.0 ≤ v < 6.4.157.0.0 ≤ v ≤ 7.0.117.0.0 ≤ v < 7.0.127.2.0 ≤ v ≤ 7.2.47.2.0 ≤ v < 7.2.57.4.0 ≤ v ≤ 7.4.27.4.0 ≤ v < 7.4.36.2.06.2.16.2.106.2.116.2.126.2.136.2.26.2.36.2.46.2.56.2.66.2.76.2.86.2.96.4.06.4.16.4.106.4.116.4.126.4.136.4.146.4.26.4.36.4.46.4.56.4.66.4.76.4.86.4.97.0.07.0.17.0.107.0.117.0.27.0.37.0.47.0.57.0.67.0.77.0.87.0.97.2.07.2.17.2.27.2.37.2.47.4.07.4.17.4.2
Affected range stops below 6.2.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.2.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.4.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.2.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.4.5, so it looks safe — our inference, not a vendor statement
2.0.0 ≤ v ≤ 2.0.142.0.0 ≤ v < 7.0.167.0.0 ≤ v ≤ 7.0.157.2.0 ≤ v ≤ 7.2.97.2.0 ≤ v < 7.2.107.4.0 ≤ v ≤ 7.4.27.4.0 ≤ v < 7.4.32.0.07.0.07.2.07.4.0
Affected range stops below 7.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.2.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.4.3, so it looks safe — our inference, not a vendor statement
6.0.0 ≤ v < 6.4.97.0.0 ≤ v < 7.0.3
Affected range stops below 6.4.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.3, so it looks safe — our inference, not a vendor statement
7.4.0 ≤ v < 7.4.3
Affected range stops below 7.4.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-923

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card