FortimanagerApplication · Fortinet
CVE-2023-36554
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 improper access control in Fortinet FortiManager version 7.4.0, version 7.2.0 through 7.2.3, version 7.0.0 through 7.0.10, version 6.4.0 through 6.4.13, 6.2 all versions allows attacker to execute unauthorized code or commands via specially crafted HTTP 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 confidenceAn improper access control vulnerability in Fortinet FortiManager allows unauthenticated remote attackers to execute arbitrary code or commands through specially crafted HTTP requests. This is a critical RCE flaw affecting multiple versions of the enterprise network management appliance.
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
>= 6.2.0, <= 6.2.12>= 6.4.0, <= 6.4.13>= 7.0.0, <= 7.0.10>= 7.2.0, <= 7.2.3= 7.4.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Check FortiManager firmware version via CLILog into the FortiManager CLI and run the command: get system status. Look for the version field (e.g., Firmware Version: 7.0.x)Affected if The displayed version falls within any of these ranges: 6.2.0-6.2.12, 6.4.0-6.4.13, 7.0.0-7.0.10, 7.2.0-7.2.3, or 7.4.0
-
Verify management interface exposureCheck the network configuration via the FortiManager CLI using: show system interface. Identify which interfaces have https (port 443) or http (port 80) services enabled and whether they are bound to external/untrusted networksAffected if The management interface (HTTPS/HTTP) is bound to a WAN or untrusted network interface accessible from the internet or less trusted networks
-
Review HTTP access logs for unauthenticated requestsExamine FortiManager logs for HTTP requests to the management interface from unauthenticated sources. In the web UI, go to Log & Report -> Event Log -> Web Proxy or check system event logs for failed authentication attempts with unusual request patternsAffected if Unusual HTTP requests are observed in logs, especially those targeting API endpoints without prior authentication or from unexpected source IPs
-
Confirm FMG process listening on management portsRun: diagnose system service or netstat on the FortiManager to confirm the fmgd service is listening on ports 80/443 (or custom management ports). Run: diagnose hardware device list or check the web UI under System Settings -> Administration -> Administrators to verify admin access is enabledAffected if The FortiManager management service is active and accessible on standard or custom HTTP/HTTPS ports without additional network segmentation
You are affected if your FortiManager firmware version is 6.2.0-6.2.12, 6.4.0-6.4.13, 7.0.0-7.0.10, 7.2.0-7.2.3, or exactly 7.4.0, AND the management interface is network-accessible to attackers.
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 · scopedApply the vendor-supplied patch to update FortiManager to a supported, patched version. If immediate patching is not possible, restrict network access to the management interface and monitor for suspicious HTTP traffic.
Upgrade to FortiManager 7.4.1 or later (or latest version in your respective branch: 6.4.14+, 7.0.11+, 7.2.4+)
- 1. Identify the current FortiManager version by navigating to System Settings > FortiManager or using the CLI command 'get system status'
- 2. Determine the appropriate upgrade path based on your current version branch (6.2.x → 6.4.x or higher, 6.4.x → 7.0.x or higher, 7.2.x → 7.4.x)
- 3. Download the upgrade image from Fortinet Customer Support portal (https://support.fortinet.com)
- 4. Back up the FortiManager configuration using the GUI (System Settings > Configuration > Backup) or CLI command 'execute backup full-config'
- 5. Upload the firmware image via GUI (System Settings > Firmware) or CLI command 'execute system firmware upgrade <image_name>','6. After upgrade, verify the version using 'get system status' and confirm the vulnerability is resolved
- 7. Review admin user accounts and access profiles to ensure no unauthorized changes were made
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortimanager
Scoped from the published advisory
- Consultation2.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36554 — 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-2023-36554 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