CVE-2020-12812
CVE-2020-12812 is a high-severity vulnerability (CVSS 3.1 base score 7.5). Fortinet FortiOS SSL VPN contains an improper authentication vulnerability that may allow a user to login successfully without being prompted for the second factor of authentication (FortiToken) if they change the case in their username. CISA added it to the Known Exploited Vulnerabilities catalog on 2021-11-03, with a remediation due date of 2022-05-03 for US federal civilian agencies. CISA lists known use in ransomware campaigns. As of 2026-11-22, EPSS estimates a 45.4% probability of exploitation in the next 30 days, in the 98th percentile of scored CVEs.
Updated
- CVSS 3.1
- 7.5 HIGH
- EPSS
- 45.4% (98th pct)
- CISA KEV
- Exploited
- Published
- 2020-07-24
- Weakness
- CWE-287
Fortinet FortiOS SSL VPN Improper Authentication Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply updates per vendor instructions.
CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2020-12812
Description
An improper authentication vulnerability in SSL VPN in FortiOS 6.4.0, 6.2.0 to 6.2.3, 6.0.9 and below may result in a user being able to log in successfully without being prompted for the second factor of authentication (FortiToken) if they changed the case of their username.
Key Findings
as of 2026-11-22- CISA added CVE-2020-12812 to the KEV catalog 467 days after its CVE record was published.
- It is one of 32 Fortinet entries in the CISA KEV catalog, and one of 4 added in 2021.
- Its current EPSS score (45.4%) is higher than that of 46% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable yes, technical impact partial, 2026-08-12).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| - | Fortinet FortiOS | FortiOS 6.4.0, 6.2.0 to 6.2.3, 6.0.9 and below |
References
1 linksOther references
Record Details
- Published
- 2020-07-24
- Last updated
- 2026-10-01
- Assigner (CNA)
- fortinet
- Credited to
- -
More from Fortinet
Fortinet FortiOS SSL VPN Path Traversal Vulnerability
Fortinet FortiOS Heap-Based Buffer Overflow Vulnerability
Fortinet FortiOS Out-of-Bound Write Vulnerability
Fortinet FortiOS Exposure of Sensitive Information to an Unauthorized Actor Vulnerability
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.