Configuration disclosure and modification via client-side controls
Published May 14, 2024 · Updated Jan 14, 2026
Authorization bypass in Fortinet FortiSandbox 4.2.1 through 4.2.6 and 4.4.0 through 4.4.4 allows remote authenticated users to alter configuration. The HTTP management interface relies on client-side controls instead of enforcing the read-only role when processing configuration upload and download requests. At least read-only permission is required; exploitation exposes device configuration and allows unauthorized replacement of it.
Summary
What happened
Authorization bypass in Fortinet FortiSandbox 4.2.1 through 4.2.6 and 4.4.0 through 4.4.4 allows remote authenticated users to alter configuration. The HTTP management interface relies on client-side controls instead of enforcing the read-only role when processing configuration upload and download requests. At least read-only permission is required; exploitation exposes device configuration and allows unauthorized replacement of it.
The record
- CVE
- CVE-2024-31491
- Published
- May 14, 2024
- Updated
- Jan 14, 2026
- Vendor
- Fortinet
- Product
- FortiSandbox
- Classifications
- CWE-602
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2024CVE publishedPublication date reported by the CVE source.
- Jan 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2.0 <=4.2.6
- Affected versionversion=4.2.1 <=4.2.6
- Affected versionversion=4.4.0 <=4.4.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo