VulnerabilityPublished 14 Oct 2025Updated 22 Oct 2026

CVE-2024-47569: Fortinet FortiManager · Information Disclosure

Affects Fortinet FortiManagerSource CVE Database V5

Public exploit available · CVSS 4.2 Medium.

Data as of 26 Oct 2026, 10:24 UTC

CVSS 3.1 base score

4.2Medium

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

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

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

Base metrics

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

Temporal metrics

Exploit Code Maturity: Functional
Remediation Level: Unavailable
Report Confidence: Confirmed

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Functional: Functional exploit code is available. The code works in most situations where the vulnerability exists.
Remediation Level: Unavailable: There is either no solution available or it is impossible to apply.
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 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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.

cwe-201

What to do

Affected software

Product	Affected	Fixed in
FortinetFortiManager	Affected >=7.6.0 <=7.6.1 >=7.4.1 <=7.4.3	Fixed in–
FortinetFortiOS	Affected >=7.4.0 <=7.4.4 >=7.2.0 <=7.2.8 >=7.0.0 <=7.0.15 >=6.4.0 <=6.4.15 >=6.2.0 <=6.2.17 >=6.0.0 <=6.0.18 =7.6.0	Fixed in–
FortinetFortiProxy	Affected >=7.4.0 <=7.4.4 >=7.2.0 <=7.2.10 >=7.0.0 <=7.0.23 >=2.0.0 <=2.0.14 >=1.2.1 <=1.2.13 >=1.1.4 <=1.1.6 >=01.01.00 <=01.01.03 >=01.00.00 <=01.00.07 =01.02.00	Fixed in–
FortinetFortiWeb	Affected >=7.4.0 <=7.4.4 >=7.2.0 <=7.2.13 >=7.0.0 <=7.0.12 >=6.4.0 <=6.4.3 =7.6.0	Fixed in–
FortinetFortiVoice	Affected >=7.0.0 <=7.0.4 >=6.4.0 <=6.4.9 >=6.0.7 <=6.0.12	Fixed in–
FortinetFortiTester	Affected >=7.4.0 <=7.4.2 >=7.3.0 <=7.3.2 >=7.2.0 <=7.2.3 >=7.1.0 <=7.1.1 >=4.2.0 <=4.2.1 =7.0.0	Fixed in–

CPE configurations (218)

cpe:2.3:a:fortinet:fortiproxy:7.4.4:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortiproxy:7.4.3:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortiproxy:7.4.2:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortiproxy:7.4.1:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortiproxy:7.4.0:*:*:*:*:*:*:*
cpe:2.3:a:fortinet:fortiproxy:7.2.10:*:*:*:*:*:*:*

AI-suggested

European organizations should implement the following specific mitigations: 1) Immediately inventory all Fortinet products in use, focusing on FortiManager Cloud 7.4.1 and other affected versions listed. 2) Apply any available patches or firmware updates from Fortinet as soon as they are released. 3) Restrict network access to management interfaces using segmentation, VPNs, or firewall rules to limit exposure to trusted administrators only. 4) Enforce strong authentication mechanisms and monitor for unusual login activity to reduce risk from compromised credentials. 5) Enable detailed logging and alerting on Fortinet devices to detect anomalous packet traffic indicative of exploitation attempts. 6) Conduct regular security audits and vulnerability scans focusing on Fortinet infrastructure. 7) If patches are not yet available, consider temporary workarounds such as disabling vulnerable services or features where feasible. 8) Train security teams on the specifics of this vulnerability to improve detection and response capabilities. 9) Coordinate with Fortinet support for guidance and early access to fixes. 10) Review and update incident response plans to include scenarios involving Fortinet product compromise.

Description

A insertion of sensitive information into sent data vulnerability in Fortinet FortiMail 7.4.0 through 7.4.2, FortiMail 7.2.0 through 7.2.6, FortiMail 7.0 all versions, FortiManager 7.6.0 through 7.6.1, FortiManager 7.4.1 through 7.4.3, FortiManager Cloud 7.4.1 through 7.4.3, FortiNDR 7.6.0 through 7.6.1, FortiNDR 7.4.0 through 7.4.8, FortiNDR 7.2 all versions, FortiNDR 7.1 all versions, FortiNDR 7.0 all versions, FortiNDR 1.5 all versions, FortiOS 7.6.0, FortiOS 7.4.0 through 7.4.4, FortiOS 7.2.0 through 7.2.8, FortiOS 7.0.0 through 7.0.15, FortiOS 6.4.0 through 6.4.15, FortiOS 6.2 all versions, FortiOS 6.0 all versions, FortiPAM 1.3 all versions, FortiPAM 1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiProxy 7.4.0 through 7.4.4, FortiProxy 7.2.0 through 7.2.10, FortiProxy 7.0 all versions, FortiProxy 2.0 all versions, FortiProxy 01.02 all versions, FortiProxy 1.2 all versions, FortiProxy 01.01 all versions, FortiProxy 1.1 all versions, FortiProxy 01.00 all versions, FortiRecorder 7.2.0 through 7.2.1, FortiRecorder 7.0.0 through 7.0.4, FortiTester 7.4.0 through 7.4.2, FortiTester 7.3 all versions, FortiTester 7.2 all versions, FortiTester 7.1 all versions, FortiTester 7.0 all versions, FortiTester 4.2 all versions, FortiVoice 7.0.0 through 7.0.4, FortiVoice 6.4.0 through 6.4.9, FortiVoice 6.0.7 through 6.0.12, 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 disclose sensitive information via specially crafted packets.

Impact

For European organizations, the impact of CVE-2024-47569 is primarily the unauthorized disclosure of sensitive information, which could include configuration details, credentials, or operational data from Fortinet security infrastructure. This exposure can facilitate lateral movement, privilege escalation, or targeted attacks against critical network components. Organizations relying heavily on Fortinet products for network security, especially FortiManager Cloud for centralized management, face increased risk of data leakage. The breach of confidentiality could undermine compliance with GDPR and other data protection regulations, leading to legal and reputational consequences. Since the vulnerability requires authentication, insider threats or compromised credentials pose a significant risk vector. The broad product impact means that organizations with diverse Fortinet deployments must assess multiple systems for exposure. The lack of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once details are public. The medium severity rating suggests that while the vulnerability is not critical, it warrants timely remediation to prevent escalation.

References

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

Community reviews

Loading reviews…