FortiportalApplication · Fortinet
CVE-2021-36168
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Fortinet FortiPortal 6.x before 6.0.5, FortiPortal 5.3.x before 5.3.6 and any FortiPortal before 6.2.5 allows authenticated attacker to disclosure information via crafted GET request with malicious parameter values.
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 · moderate confidenceFortiPortal versions before 6.0.5, 5.3.6, and 6.2.5 contain a path traversal vulnerability allowing authenticated attackers to access sensitive files outside the web root directory via crafted GET requests containing directory traversal sequences (e.g., ../../../) in parameters.
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
FortiportalApplication
< 5.2.6>= 5.3.0, < 5.3.6>= 6.0.0, < 6.0.5CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 FortiPortal versionAccess the FortiPortal admin interface or check system information page, typically found under System > Settings or by querying the FortiPortal API endpoint for version informationAffected if The installed version falls within < 5.2.6, >= 5.3.0 and < 5.3.6, or >= 6.0.0 and < 6.0.5
-
Verify authentication method is enabledConfirm that user authentication is configured and accessible for FortiPortal management interfaceAffected if User authentication is enabled, which is required for the attacker to exploit the path traversal
-
Identify vulnerable parameter handlingReview HTTP GET request logs or proxy traffic for parameters containing directory traversal sequences (e.g., ../../../) sent to FortiPortal endpointsAffected if GET requests with ../ sequences in parameters are being processed by FortiPortal, indicating the vulnerable code path is reachable
If FortiPortal version is below 6.0.5 (for 6.0.x), below 5.3.6 (for 5.3.x), or below 5.2.6, and the application processes authenticated requests containing directory traversal sequences, the environment is affected by this CVE.
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 data5.2.65.3.66.0.5
Upgrade FortiPortal to version 6.0.5 (for 6.x branch), 5.3.6 (for 5.3.x branch), or 6.2.5 or later. If immediate patching is not possible, limit FortiPortal administrative access to trusted personnel only.
Fix this in Fortiportal
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36168 — 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-2021-36168 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