VulnerabilityPublished 14 Jan 2025Updated 4 Feb 2026

CVE-2024-45326: Fortinet FortiDeceptor · Improper Access Control

Affects Fortinet FortiDeceptorSource CVE Database V5

Public exploit available · CVSS 3.9 Low.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score

3.9Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% 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:N/I:L/A:N/E:P/RL:X/RC:R

Base metrics

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

Temporal metrics

Exploit Code Maturity: Proof-of-Concept
Report Confidence: Reasonable

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: 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.
Report Confidence: Reasonable: Significant details are published, but researchers either do not have full confidence in the root cause, or do not have access to source code to fully confirm all of the interactions that may lead to the result. Reasonable confidence exists, however, that the bug is reproducible and at least one impact is able to be verified (Proof-of-concept exploits may provide this). An example is a detailed write-up of research into a vulnerability with an explanation (possibly obfuscated or 'left as an exercise to the reader') that gives assurances on how to reproduce the results.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jan 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.

What to do

Affected software

Product	Affected	Fixed in
Fortinet FortiDeceptor	Affected 5.0.0 – 6.0.0 5 affected builds	Fixed in–

AI-suggested

Organizations should implement the following specific mitigations: 1) Immediately inventory all FortiDeceptor deployments and identify affected versions (5.0.0 through 6.0.0). 2) Apply vendor patches or updates as soon as they become available to address CVE-2024-45326. 3) Restrict access to the FortiDeceptor central management appliance by enforcing network segmentation and limiting management interface exposure to trusted administrative networks only. 4) Enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. 5) Monitor management appliance logs and network traffic for unusual or unauthorized operations indicative of exploitation attempts. 6) Conduct regular audits of user privileges and remove unnecessary accounts or permissions. 7) Consider deploying additional detection controls to identify anomalous changes in deception configurations. 8) Educate administrators on the risks of low-privilege account misuse and encourage prompt reporting of suspicious activity. These targeted actions go beyond generic advice by focusing on access control hardening and operational monitoring specific to FortiDeceptor environments.

Description

An Improper Access Control vulnerability [CWE-284] vulnerability in Fortinet FortiDeceptor 6.0.0, FortiDeceptor 5.3 all versions, FortiDeceptor 5.2 all versions, FortiDeceptor 5.1 all versions, FortiDeceptor 5.0 all versions may allow an authenticated attacker with none privileges to perform operations on the central management appliance via crafted requests.

Impact

For European organizations, the impact primarily concerns the integrity of security monitoring and threat detection capabilities. If an attacker exploits this vulnerability, they could alter deception configurations or disable certain traps, reducing the effectiveness of FortiDeceptor in detecting lateral movement or insider threats. This could lead to prolonged undetected intrusions and increased risk of data breaches or operational disruption. Since FortiDeceptor is often deployed in critical infrastructure, financial institutions, and large enterprises, the ability to manipulate its management interface could have cascading effects on overall security posture. However, the lack of confidentiality or availability impact limits direct data loss or service outages from this vulnerability alone. The requirement for authentication limits exploitation to insiders or attackers who have compromised low-privilege credentials, which is a common scenario in targeted attacks. European entities relying on Fortinet solutions should consider this vulnerability a risk to their layered defense strategy, especially in sectors with high regulatory requirements for cybersecurity.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Feb 2026, 14:29 UTC

Technical details

References

Community reviews

Related threats