FortiwlmApplication · Fortinet
CVE-2023-36548
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 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 · high confidenceOS command injection vulnerability in Fortinet FortiWLM web interface allows remote attackers to execute arbitrary operating system commands via specially crafted HTTP GET request parameters in affected versions 8.5.0-8.5.4 and 8.6.0-8.6.5.
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.5.0, <= 8.5.4>= 8.6.0, <= 8.6.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm FortiWLM is installedIdentify if Fortinet FortiWLM (wireless LAN manager) software is running in your environment. Check system inventory, running processes, or network services for 'FortiWLM', 'fortiwlm', or port 8080/443 management services.Affected if FortiWLM is present in your environment
-
Determine installed versionAccess the FortiWLM management interface or CLI and retrieve the software version. Common methods include: logging into the web UI and checking the dashboard/system status page, or running 'get system status' or 'fwlua -v' via CLI.Affected if The installed version falls within 8.5.0-8.5.4 or 8.6.0-8.6.5
-
Verify web interface is enabledCheck if the FortiWLM web management interface (HTTP/HTTPS) is enabled and accessible. This can be done by attempting to reach the management IP on ports 80 or 443, or checking the configuration via CLI for 'httpd' or 'webui' settings.Affected if The web interface is enabled and reachable
-
Assess network exposureDetermine if the FortiWLM management interface is exposed to untrusted networks. Review firewall rules, ACLs, and interface bindings to see if the web UI is accessible from outside your trusted internal networks.Affected if The management web interface is accessible from untrusted networks or the internet
You are affected if FortiWLM version 8.5.0-8.5.4 or 8.6.0-8.6.5 is installed with the web management interface enabled and exposed, as the command injection occurs via HTTP GET parameters in the web interface.
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 dataApply Fortinet vendor patches (version 8.6.6 or 8.5.5 and later) to remediate; restrict management interface access to trusted networks until patched.
Fix this in Fortiwlm
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-36548 — 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-36548 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