CVE-2025-54822VulnerabilityPublished 14 Oct 2025Updated 14 Jan 2026

CVE-2025-54822: Fortinet FortiProxy · Improper Access Control

Affects Fortinet FortiProxySource CVE Database V5

Not known to be exploited · CVSS 4.2 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.2Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% 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:X/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
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.
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: 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 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 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 FortiProxy	Affected =7.4.0 =7.2.0 =7.0.0 =2.0.0	Fixed in–

AI-suggested

To mitigate CVE-2025-54822, European organizations should: 1) Immediately identify and inventory all Fortinet FortiProxy and FortiOS devices running affected versions, especially those configured with multiple VDOMs. 3) Restrict administrative and user access to Fortinet devices to the minimum necessary privileges, enforcing strong authentication mechanisms such as multi-factor authentication (MFA). 4) Monitor device logs for unusual HTTP/HTTPS requests that may indicate attempts to access unauthorized VDOM files. 5) Implement network segmentation and access controls to limit exposure of management interfaces to trusted networks only. 6) Conduct regular security audits and penetration tests focusing on multi-VDOM configurations to detect potential access control weaknesses. 7) Educate administrators about the risks of improper access control and the importance of promptly applying security updates. These steps will reduce the attack surface and help prevent exploitation of the vulnerability.

Description

An improper authorization vulnerability [CWE-285] vulnerability in Fortinet FortiOS 7.4.0 through 7.4.1, FortiOS 7.2.0 through 7.2.8, FortiOS 7.0.0 through 7.0.11, FortiProxy 7.4.0 through 7.4.8, FortiProxy 7.2 all versions, FortiProxy 7.0 all versions, FortiProxy 2.0 all versions allows an authenticated attacker to access static files of others VDOMs via crafted HTTP or HTTPS requests.

Impact

For European organizations, the impact of CVE-2025-54822 centers on unauthorized disclosure of sensitive information across VDOM boundaries within Fortinet FortiProxy and FortiOS devices. Many enterprises and service providers in Europe rely on Fortinet products for secure network segmentation and traffic management. Exploitation could allow attackers with authenticated access—potentially via compromised credentials or insider threats—to access static files containing configuration data or other sensitive information from other VDOMs, potentially exposing network topology, security policies, or other confidential data. While the vulnerability does not allow modification or disruption of services, the confidentiality breach could facilitate further attacks or lateral movement within segmented networks. This risk is particularly relevant for organizations with strict data protection requirements under GDPR, as unauthorized data exposure could lead to compliance violations and reputational damage. The absence of known exploits reduces immediate risk, but the medium severity rating and broad product impact necessitate timely mitigation to prevent potential exploitation.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 14:48 UTC

Technical details

References

Community reviews

Related threats