Fortinet FortiWLC up to 8.5.2 Managed Access Point hard-coded password
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Fortinet FortiWLC up to 8.2.7/8.3.3/8.4.2/8.4.8/8.5.2. Impacted is an unknown function of the component Managed Access Point. The manipulation leads to hard-coded password. This vulnerability is traded as CVE-2021-22126. An attack has to be approached locally. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Fortinet FortiWLC up to 8.2.7/8.3.3/8.4.2/8.4.8/8.5.2. This issue affects an unknown functionality of the component Managed Access Point. The manipulation with an unknown input leads to a hard-coded password vulnerability. Using CWE to declare the problem leads to CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A use of hard-coded password vulnerability in FortiWLC version 8.5.2 and below, version 8.4.8 and below, version 8.3.3 to 8.3.2, version 8.2.7 to 8.2.6 may allow a local, authenticated attacker to connect to the managed Access Point (Meru AP and FortiAP-U) as root using the default hard-coded username and password.
The advisory is shared at fortiguard.fortinet.com. The identification of this vulnerability is CVE-2021-22126 since 01/04/2021. The exploitation is known to be easy. An attack has to be approached locally. Additional levels of successful authentication are needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1078.001 for this issue.
Upgrading eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 8.2.0
- 8.2.1
- 8.2.2
- 8.2.3
- 8.2.4
- 8.2.5
- 8.2.6
- 8.2.7
- 8.3.0
- 8.3.1
- 8.3.2
- 8.3.3
- 8.4.0
- 8.4.1
- 8.4.2
- 8.4.3
- 8.4.4
- 8.4.5
- 8.4.6
- 8.4.7
- 8.4.8
- 8.5.0
- 8.5.1
- 8.5.2
License
Website
- Vendor: https://www.fortinet.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.7
CNA Vector (fortinet): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded passwordCWE: CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
01/04/2021 🔍03/17/2025 🔍
03/17/2025 🔍
07/25/2025 🔍
Sources
Vendor: fortinet.comAdvisory: FG-IR-20-147
Status: Confirmed
CVE: CVE-2021-22126 (🔍)
GCVE (CVE): GCVE-0-2021-22126
GCVE (VulDB): GCVE-100-299909
Entry
Created: 03/17/2025 14:43Updated: 07/25/2025 01:08
Changes: 03/17/2025 14:43 (64), 07/25/2025 01:08 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.