CVE-2023-34991: Fortinet FortiWLM · Execute unauthorized code or commands
Affects Fortinet FortiWLMSource CVE Database V5
Not known to be exploited · 28% EPSS · CVSS 9.3 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 28.7% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:XExploitation evidence
Disclosed: evidence found.
CVE published 14 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Fortinet FortiWLM | Affected
| Fixed in– |
AI-suggested
1. Immediate network-level mitigations: Implement strict firewall rules to restrict access to FortiWLM management interfaces, allowing only trusted IP addresses and internal networks. 2. Network segmentation: Isolate FortiWLM systems from general user networks to limit potential lateral movement in case of compromise. 3. Monitor HTTP traffic: Deploy intrusion detection/prevention systems (IDS/IPS) and web application firewalls (WAF) to detect and block suspicious HTTP requests containing SQL injection patterns targeting FortiWLM. 4. Apply vendor patches promptly: Although no patches were listed at the time of reporting, monitor Fortinet advisories closely and apply updates as soon as they become available. 5. Conduct vulnerability scanning and penetration testing focused on FortiWLM instances to identify exposure. 6. Harden FortiWLM configurations by disabling unnecessary services and enforcing strong access controls. 7. Maintain comprehensive logging and alerting on FortiWLM systems to detect anomalous activities early. 8. Educate network and security teams about this specific vulnerability to ensure rapid response capability. These steps go beyond generic advice by focusing on network controls, monitoring, and proactive detection tailored to FortiWLM environments.
Description
CVE-2023-34991 is a critical SQL injection vulnerability in Fortinet FortiWLM versions 8.2.2 through 8.6.5 that allows unauthenticated remote attackers to execute arbitrary code or commands via crafted HTTP requests. This vulnerability enables full compromise of affected systems without requiring user interaction or authentication. The flaw arises from improper neutralization of special elements in SQL commands, leading to unauthorized code execution. Although no known exploits are currently reported in the wild, the high CVSS score of 9.3 indicates significant risk. European organizations using FortiWLM for wireless LAN management are at risk of data breaches, service disruption, and potential lateral movement within networks.