dbcve.org
FortiwlmApplication · Fortinet

CVE-2021-43075

HIGH · 8.8 CVSS v3.1 Published 2022-03-01
Fix available
A fix is available. Upgrade to 8.6.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A improper neutralization of special elements used in an os command ('os command injection') in Fortinet FortiWLM version 8.6.2 and below, version 8.5.2 and below, version 8.4.2 and below, version 8.3.2 and below allows attacker to execute unauthorized code or commands via crafted HTTP requests to the alarm dashboard and controller config handlers.

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 confidence

OS command injection vulnerability in Fortinet FortiWLM allows attackers to execute arbitrary commands via crafted HTTP requests to the alarm dashboard and controller config handlers. The web interface fails to properly sanitize user input, enabling shell command injection through the HTTP parameters.

MitigationApply Fortinet's patches for this vulnerability by upgrading to a fixed version (8.6.3+, 8.5.3+, 8.4.3+, 8.3.3+). Until patched, restrict access to the FortiWLM management interface to trusted networks only.

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
Affected:<= 8.3.2>= 8.4.0, <= 8.4.2>= 8.5.0, <= 8.5.2>= 8.6.0, < 8.6.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiWLM version via CLI
    Log into the FortiWLM CLI and run the command to display system information, typically `get system status` or `diag sys version`
    Affected if The displayed version falls within any of these ranges: <=8.3.2, 8.4.0-8.4.2, 8.5.0-8.5.2, or 8.6.0-8.6.2 (versions before the fixed releases 8.3.3, 8.4.3, 8.5.3, 8.6.3)
  2. Check FortiWLM version via web UI
    Log into the FortiWLM web interface and navigate to the system information or about page, typically under System > Settings or Help > About
    Affected if The version shown matches any of the vulnerable ranges listed above
  3. Determine if web management interface is network-accessible
    Review firewall rules or access control lists to confirm whether the FortiWLM web interface (ports 443 or 8080) is reachable from untrusted or external networks
    Affected if The management interface is exposed to networks that are not trusted or are externally accessible
  4. Verify web interface authentication status
    Attempt to access the FortiWLM login page or check configuration for whether the alarm dashboard and controller config handlers require valid authentication
    Affected if The vulnerable endpoints are accessible without requiring authentication or with weak/default credentials

You are affected if your FortiWLM version is 8.3.2 or lower, 8.4.0-8.4.2, 8.5.0-8.5.2, or 8.6.0-8.6.2 and the management web interface is accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.6.3 or later
Fixed in 8.6.3
Interim mitigation

Apply Fortinet's patches for this vulnerability by upgrading to a fixed version (8.6.3+, 8.5.3+, 8.4.3+, 8.3.3+). Until patched, restrict access to the FortiWLM management interface to trusted networks only.

Recommended fix High confidence

FortiWLM 8.6.3 or later (latest stable 8.x release)

  1. Access FortiWLM management interface or console
  2. Identify current installed version under System > Firmware or equivalent
  3. Download the fixed firmware version 8.6.3 or later from Fortinet Customer Support portal (https://support.fortinet.com)
  4. Review the FortiWLM release notes for version 8.6.3 for any migration requirements
  5. Backup current configuration before upgrade
  6. Upload and install firmware version 8.6.3 or latest available stable release
  7. Verify the upgrade completed successfully and the web UI is accessible
  8. Confirm vulnerability is remediated by checking the firmware version
Caveat Review FortiWLM 8.6.3 release notes for any configuration or feature changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortiwlm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-43075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-43075 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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