FortimanagerApplication · Fortinet
CVE-2024-32115
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA relative path traversal vulnerability [CWE-23] in Fortinet FortiManager version 7.4.0 through 7.4.2 and before 7.2.5 allows a privileged attacker to delete files from the underlying filesystem via crafted HTTP or HTTPs requests.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA relative path traversal vulnerability (CWE-23) in FortiManager versions 7.4.0-7.4.2 and before 7.2.5 allows authenticated privileged attackers to delete arbitrary files on the filesystem via crafted HTTP/HTTPS requests. The vulnerability requires authentication and involves manipulating path traversal sequences in HTTP requests to access files outside the intended web root directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FortimanagerApplication
>= 7.0.0, < 7.2.6>= 7.4.0, < 7.4.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FortiManager versionRun 'get system status' via CLI or check the login page footer/version display in the web UI. The version appears in the format like 7.4.0, 7.4.1, 7.4.2, 7.2.4, etc.Affected if Version is 7.4.0 through 7.4.2, or 7.2.0 through 7.2.5, or any 7.0.x through 7.0.x release (note: 7.2.6+ and 7.4.3+ are fixed)
-
Verify HTTP/HTTPS management interface is enabledCheck via CLI: 'get system interface' or review the network interface configuration to confirm ports 80/443 or custom HTTP/HTTPS management listeners are active.Affected if HTTP or HTTPS management interface is exposed and reachable on any listen interface
-
Confirm administrative access policyReview who has administrative credentials by checking 'diagnose system admin list' or reviewing the admin user list via web UI under System > Administrators.Affected if More than one admin account exists, or if any admin account may have been compromised or shared
-
Review access logs for suspicious path traversal patternsCheck logs under Log & Report > Event Logging > System Events, or run 'execute log filter category 1' followed by 'execute log display' looking for unusual HTTP requests with '../' patterns targeting unexpected paths.Affected if Unusual HTTP requests containing '../' sequences or unexpected file delete operations appear in logs
Your FortiManager is affected if it runs version 7.4.0-7.4.2 or 7.2.0-7.2.5 (or 7.0.x) AND has the HTTP/HTTPS management interface enabled, allowing a malicious authenticated attacker to potentially delete files outside the web root via path traversal.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.2.67.4.3
Upgrade FortiManager to version 7.4.3 or later, or version 7.2.5 or later. Apply the patch within a planned maintenance window following change management procedures.
FortiManager 7.2.6 or later, or 7.4.3 or later
- 1. Identify the current FortiManager version by accessing the Web UI or CLI
- 2. If running version 7.0.x through 7.2.5, plan upgrade to version 7.2.6 or later
- 3. If running version 7.4.0 through 7.4.2, plan upgrade to version 7.4.3 or later
- 4. Review Fortinet release notes and upgrade path documentation for your specific version
- 5. Backup the FortiManager configuration before upgrading
- 6. Perform the upgrade during a planned maintenance window
- 7. After upgrade, verify the version and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortimanager
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32115 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data