dbcve.org
FortiwlmApplication · Fortinet

CVE-2023-34987

HIGH · 8.8 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to after 8.6.5 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.0 through 8.6.5 and 8.5.0 through 8.5.4 allows attacker to execute unauthorized code or commands via specifically crafted HTTP get request parameters.

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 confidence

OS command injection vulnerability in FortiWLM allows attackers to execute unauthorized OS commands via specifically crafted HTTP GET request parameters due to improper neutralization of special elements in OS command execution.

MitigationUpgrade to FortiWLM version 8.6.6 or later (for 8.6.x) or 8.5.5 or later (for 8.5.x). Alternatively, implement strict input validation and avoid using user-supplied input in OS command execution.

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.5.0, <= 8.5.4>= 8.6.0, <= 8.6.5

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
    Access the FortiWLM administration interface or check system documentation to confirm the installed version number
    Affected if The installed version falls within 8.5.0 to 8.5.4 or 8.6.0 to 8.6.5
  2. Determine web interface exposure
    Check network configuration to see if the FortiWLM web interface is accessible from untrusted networks or the internet
    Affected if The web interface is exposed to networks where untrusted users can send HTTP requests
  3. Review HTTP access logs
    Examine FortiWLM web server access logs for anomalous GET request patterns that may contain command injection attempts
    Affected if Logs show suspicious GET requests with unexpected parameters that could indicate exploitation attempts

The environment is affected if FortiWLM version is 8.5.0-8.5.4 or 8.6.0-8.6.5 and the web interface is accessible to potential attackers

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 a release after 8.6.5
Interim mitigation

Upgrade to FortiWLM version 8.6.6 or later (for 8.6.x) or 8.5.5 or later (for 8.5.x). Alternatively, implement strict input validation and avoid using user-supplied input in OS command execution.

Recommended fix Moderate confidence

FortiWLM version 8.5.5 or later for the 8.5.x branch; version 8.6.6 or later for the 8.6.x branch (or the latest available stable release)

  1. 1. Identify the current FortiWLM version using the web UI or CLI: `get system status` or check the dashboard.
  2. 2. Access Fortinet FortiGuard portal (https://www.fortiguard.com) or Fortinet Customer Service portal to obtain the latest patched version for FortiWLM.
  3. 3. Download the firmware upgrade file for the fixed version.
  4. 4. Backup the current FortiWLM configuration before upgrading.
  5. 5. Upload and install the new firmware via the web UI (System > Firmware) or CLI: `execute upgrade` command.
  6. 6. After reboot, verify the new version is installed and the web UI is accessible.
  7. 7. Validate that the command injection vulnerability is no longer present by confirming the fix is applied.
Caveat Review Fortinet release notes for any configuration changes or migration requirements between minor versions; ensure backup and tested rollback plan before production upgrade

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34987 — 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-2023-34987 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