FortisiemApplication · Fortinet
CVE-2023-40714
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 in Fortinet FortiSIEM versions 7.0.0, 6.7.0 through 6.7.2, 6.6.0 through 6.6.3, 6.5.1, 6.5.0 allows attacker to escalate privilege via uploading certain GUI elements
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 in FortiSIEM's GUI upload functionality allows attackers to write files to arbitrary locations on the filesystem, leading to privilege escalation. The attacker exploits insufficient path validation when uploading GUI elements, potentially overwriting configuration files or placing executable code in privileged locations.
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
>= 6.4.0, <= 6.5.1>= 6.6.0, <= 6.6.3>= 6.7.0, <= 6.7.3= 7.0.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 versionRun the command to display the FortiSIEM version, typically via the CLI with 'phoenixctl --get-version' or check the system information in the GUI under Admin > System Settings > General. Compare the displayed version number against the affected ranges: 6.4.0-6.5.1, 6.6.0-6.6.3, 6.7.0-6.7.3, and 7.0.0.Affected if The installed version falls within any of the listed affected ranges.
-
Confirm GUI access is enabledCheck if the FortiSIEM web GUI service is running and accessible. This can be verified by attempting to reach the GUI login page over HTTPS or by checking the service status via CLI.Affected if The GUI is exposed and accessible to users or attackers.
-
Review recent GUI file upload logsExamine FortiSIEM event logs and system logs for file upload operations, particularly those involving GUI element uploads. Look for uploads containing path traversal sequences like '../' in filenames or unusual upload destinations.Affected if Logs show file uploads with path traversal patterns or uploads to unexpected directories.
-
Check for unauthorized configuration changesReview system configuration files and administrative account changes. Look for new privileged user accounts, modified authentication settings, or changes to scheduled tasks or scripts that were not initiated by legitimate administrators.Affected if Unexpected configuration modifications, new admin accounts, or modified system files are present.
-
Inspect filesystem for suspicious filesSearch the filesystem for newly created files in privileged directories such as /opt, /home, or system configuration directories. Focus on directories where uploaded content would not normally be placed by standard FortiSIEM operations.Affected if Executable files or scripts are found in locations where they should not exist or were not intentionally deployed.
A defender is affected if their FortiSIEM version falls within the vulnerable ranges AND the GUI is accessible, regardless of whether exploitation is confirmed.
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 a patched version beyond 7.0.0, 6.7.2, 6.6.3, or 6.5.1 as specified in Fortinet's advisory. If immediate patching is not possible, restrict GUI access to trusted users and monitor for anomalous file upload activities.
Fix this in Fortisiem
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40714 — 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-40714 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