CVE-2025-54822: Improper access control in Fortinet FortiProxy
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.
AI Analysis
Technical Summary
CVE-2025-54822 is an improper access control vulnerability classified under CWE-285, affecting Fortinet FortiProxy and FortiOS products across multiple versions (FortiProxy 2.0.0, 7.0.x, 7.2.x, 7.4.x and FortiOS 7.0.x, 7.2.x, 7.4.x). The vulnerability arises from insufficient authorization checks when handling HTTP or HTTPS requests targeting static files associated with different Virtual Domains (VDOMs). VDOMs are logical partitions within Fortinet devices that allow segmentation of network traffic and administrative domains. Due to this flaw, an authenticated attacker with limited privileges can craft specific requests to access static files belonging to other VDOMs, thereby bypassing intended access restrictions. This exposure can lead to unauthorized disclosure of sensitive configuration or operational data stored in these files. The vulnerability does not impact data integrity or availability, nor does it require user interaction, but it does require the attacker to have some level of authenticated access to the device. The CVSS v3.1 base score is 4.2, reflecting a medium severity primarily due to the confidentiality impact and the requirement for authentication. No public exploit code or active exploitation has been reported as of the publication date. The vulnerability affects a broad range of Fortinet products widely deployed in enterprise and service provider environments, especially where multi-VDOM configurations are used for network segmentation and management.
Potential 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.
Mitigation Recommendations
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. 2) Apply vendor-supplied patches or updates as soon as they become available; monitor Fortinet advisories closely since no patch links were provided at the time of disclosure. 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.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Belgium, Sweden, Poland, Switzerland
CVE-2025-54822: Improper access control in Fortinet FortiProxy
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-54822 is an improper access control vulnerability classified under CWE-285, affecting Fortinet FortiProxy and FortiOS products across multiple versions (FortiProxy 2.0.0, 7.0.x, 7.2.x, 7.4.x and FortiOS 7.0.x, 7.2.x, 7.4.x). The vulnerability arises from insufficient authorization checks when handling HTTP or HTTPS requests targeting static files associated with different Virtual Domains (VDOMs). VDOMs are logical partitions within Fortinet devices that allow segmentation of network traffic and administrative domains. Due to this flaw, an authenticated attacker with limited privileges can craft specific requests to access static files belonging to other VDOMs, thereby bypassing intended access restrictions. This exposure can lead to unauthorized disclosure of sensitive configuration or operational data stored in these files. The vulnerability does not impact data integrity or availability, nor does it require user interaction, but it does require the attacker to have some level of authenticated access to the device. The CVSS v3.1 base score is 4.2, reflecting a medium severity primarily due to the confidentiality impact and the requirement for authentication. No public exploit code or active exploitation has been reported as of the publication date. The vulnerability affects a broad range of Fortinet products widely deployed in enterprise and service provider environments, especially where multi-VDOM configurations are used for network segmentation and management.
Potential 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.
Mitigation Recommendations
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. 2) Apply vendor-supplied patches or updates as soon as they become available; monitor Fortinet advisories closely since no patch links were provided at the time of disclosure. 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.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- fortinet
- Date Reserved
- 2025-07-30T08:31:12.197Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68ee702c75ce224a0426b911
Added to database: 10/14/2025, 3:45:48 PM
Last enriched: 1/14/2026, 2:48:21 PM
Last updated: 1/19/2026, 9:57:10 AM
Views: 76
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-1148: Cross-Site Request Forgery in SourceCodester Patients Waiting Area Queue Management System
MediumCVE-2026-1147: Cross Site Scripting in SourceCodester Patients Waiting Area Queue Management System
Medium19th January – Threat Intelligence Report
MediumCVE-2026-1146: Cross Site Scripting in SourceCodester Patients Waiting Area Queue Management System
MediumCVE-2025-59355: CWE-532 Insertion of Sensitive Information into Log File in Apache Software Foundation Apache Linkis
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.