FortiwlmApplication · Fortinet
CVE-2021-43070
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 · uneditedMultiple relative path traversal vulnerabilities [CWE-23] in FortiWLM management interface 8.6.2 and below, 8.5.2 and below, 8.4.2 and below, 8.3.3 and below, 8.2.2 may allow an authenticated attacker to retrieve arbitrary files from the underlying filesystem via specially crafted web 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 confidenceMultiple relative path traversal vulnerabilities (CWE-23) in FortiWLM management interface allow authenticated attackers to retrieve arbitrary files from the underlying filesystem via specially crafted web requests. The vulnerability exists in versions 8.6.2 and below through 8.2.2, affecting the web interface's file handling logic.
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
FortiwlmApplication
>= 8.3.0, <= 8.3.3>= 8.4.0, <= 8.4.2>= 8.5.0, <= 8.5.2>= 8.6.0, <= 8.6.2= 8.2.2CVSS 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 FortiWLM installed versionLog into the FortiWLM CLI or check the system information page in the web UI. In the CLI, run the command: exec -t get system status or check the login page footer which sometimes displays the version.Affected if The displayed version matches any of these ranges: 8.3.0-8.3.3, 8.4.0-8.4.2, 8.5.0-8.5.2, 8.6.0-8.6.2, or equals exactly 8.2.2
-
Confirm web management interface is enabledVerify the FortiWLM web server is running by attempting to access the management URL (typically https://<device-ip>/) or check the service status via CLI: exec -t get hardware health or similar system status commands that confirm the webui daemon is active.Affected if The web interface responds and is accessible, indicating the vulnerable component is exposed
-
Check interface network exposureReview firewall rules or network access lists that govern reachability to FortiWLM management ports (default HTTPS 443). Determine if the web interface is reachable from untrusted networks by reviewing perimeter firewall configurations or performing a port scan of the management IP on ports 80/443.Affected if The management interface is reachable from networks outside the trusted administrative zone
-
Verify authentication is required for the path traversalConfirm that valid credentials exist for the FortiWLM management interface. Check if default accounts remain active or if brute-force attacks could succeed. Review authentication logs for failed login attempts.Affected if An attacker can obtain valid credentials or the interface accepts authentication, which is required to exploit the path traversal flaw
A system is affected if it runs FortiWLM version 8.2.2, 8.3.0-8.3.3, 8.4.0-8.4.2, 8.5.0-8.5.2, or 8.6.0-8.6.2 AND has the web management interface exposed and accessible with valid credentials.
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 · scopedUpgrade FortiWLM to a patched version beyond the affected releases (8.6.2, 8.5.2, 8.4.2, 8.3.3, 8.2.2). If immediate patching is not possible, restrict network access to the management interface to trusted IPs only to reduce attack surface.
Upgrade to FortiWLM 8.3.4+ (8.3 branch), 8.4.3+ (8.4 branch), 8.5.3+ (8.5 branch), or 8.6.3+ (8.6 branch)
- 1. Identify the current FortiWLM version installed by accessing the management interface or running 'get system status' command
- 2. Determine which version branch is currently in use (8.3.x, 8.4.x, 8.5.x, or 8.6.x)
- 3. For 8.3.x branch: upgrade to version 8.3.4 or later
- 4. For 8.4.x branch: upgrade to version 8.4.3 or later
- 5. For 8.5.x branch: upgrade to version 8.5.3 or later
- 6. For 8.6.x branch: upgrade to version 8.6.3 or later
- 7. Download the appropriate firmware from Fortinet support portal (https://support.fortinet.com)
- 8. Upload the new firmware via the FortiWLM web interface under System > Firmware or via CLI using 'execute firmware upgrade'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiwlm
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43070 — 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-43070 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