FortisiemApplication · Fortinet
CVE-2023-36553
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 neutralization of special elements used in an os command ('os command injection') in Fortinet FortiSIEM version 5.4.0 and 5.3.0 through 5.3.3 and 5.2.5 through 5.2.8 and 5.2.1 through 5.2.2 and 5.1.0 through 5.1.3 and 5.0.0 through 5.0.1 and 4.10.0 and 4.9.0 and 4.7.2 allows attacker to execute unauthorized code or commands via crafted API 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 confidenceFortiSIEM contains an OS command injection vulnerability in its API layer. Attackers can send specially crafted API requests containing malicious OS commands that get executed on the underlying system due to improper input sanitization. This allows complete remote code execution without authentication.
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
FortisiemApplication
>= 5.1.0, <= 5.1.3= 4.7.2= 4.9.0= 4.10.0= 5.0.0= 5.0.1= 5.2.1= 5.2.2= 5.2.5= 5.2.6= 5.2.7= 5.2.8CVSS 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.
-
Identify FortiSIEM versionAccess the FortiSIEM web UI and navigate to Admin > System Settings > System Info, or use the CLI command 'phoenixctl --get version' to retrieve the installed version numberAffected if The installed version matches any of these: 4.7.2, 4.9.0, 4.10.0, 5.0.0, 5.0.1, 5.1.0 through 5.1.3, 5.2.1, 5.2.2, 5.2.5, 5.2.6, 5.2.7, or 5.2.8
-
Verify API exposureCheck network configuration to determine if the FortiSIEM API interface (typically port 443 or the /phoenix API endpoint) is accessible from untrusted networksAffected if The API is reachable from the internet or from untrusted internal networks without IP allowlisting
-
Review API access logsExamine FortiSIEM logs under System > Event Log > System > Audit for unusual or suspicious API requests, especially those containing shell metacharacters or unexpected command-like stringsAffected if Logs show API requests with unusual characters, unexpected command patterns, or signs of injection attempts
-
Check for unauthorized accessReview authentication logs for API access attempts that succeeded without proper credentials or from unexpected source IPsAffected if There are API authentication failures followed by successful unauthenticated requests, or API access from unknown IP addresses
Your environment is affected if FortiSIEM is running any version between 4.7.2 and 5.2.8 as listed, and the API interface is accessible to untrusted parties.
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.
From vendor dataUpgrade FortiSIEM to the vendor's latest patched version. Until patched, restrict network access to the API interface to trusted sources only and monitor for suspicious API activity.
Fix this in Fortisiem
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36553 — 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-36553 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