CVE-2024-54020VulnerabilityPublished 28 May 2025

CVE-2024-54020: Fortinet FortiManager · Improper access control

Affects Fortinet FortiManagerSource CVE Database V5

Not known to be exploited · CVSS 2.1 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

2.1Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C

Base metrics

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Temporal metrics

Exploit Code Maturity: Proof-of-Concept
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Proof-of-Concept: Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Fortinet FortiManager	Affected =7.2.0 =7.0.0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately verify and restrict administrative access to FortiManager instances, ensuring that only trusted personnel have high privilege accounts. 2) Monitor and audit update request logs for unusual or unauthorized changes to global threat feeds. 4) Implement network segmentation to isolate FortiManager management interfaces from general network access, reducing the attack surface. 5) Employ multi-factor authentication (MFA) for all administrative access to FortiManager to reduce the risk of credential compromise. 6) Regularly review and validate the integrity of threat feeds and security policies distributed by FortiManager to detect any unauthorized modifications early.

Description

A missing authorization in Fortinet FortiManager versions 7.2.0 through 7.2.1, and versions 7.0.0 through 7.0.7 may allow an authenticated attacker to overwrite global threat feeds via crafted update requests.

Impact

For European organizations, the impact of this vulnerability is primarily on the integrity of security management processes. If exploited, an attacker could manipulate the global threat feeds, potentially causing incorrect threat intelligence to propagate across the network security infrastructure. This could lead to false negatives or false positives in threat detection, weakening the overall security posture. Although the vulnerability does not directly compromise confidentiality or availability, the integrity breach could facilitate further attacks by allowing malicious traffic to bypass detection or causing unnecessary blocking of legitimate traffic. Organizations relying heavily on FortiManager for centralized security management, especially those in critical infrastructure sectors such as finance, energy, and government, could face increased risk of security incidents if this vulnerability is exploited. However, the requirement for high privilege authentication limits the likelihood of exploitation by external attackers without prior access.

References

fortiguard.fortinet.com/psirt/FG-IR-24-023 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Jul 2025, 01:12 UTC

Technical details

References

Community reviews

Related threats