Skip to content
Fencer Vulns
critical 9.8

CVE-2016-1909 in the critical feed json

Fortinet FortiAnalyzer before 5.0.12 and 5.2.x before 5.2.5; FortiSwitch 3.3.x before 3.3.3; FortiCache 3.0.x before 3.0.8; and FortiOS 4.1…

published 2016-01-15 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-3000

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
71.3%
EPSS 71.3% chance of exploitation in 30 days, percentile 99.4%
public exploits
2
Metasploit, Exploit-DB

Summary

Fortinet FortiAnalyzer before 5.0.12 and 5.2.x before 5.2.5; FortiSwitch 3.3.x before 3.3.3; FortiCache 3.0.x before 3.0.8; and FortiOS 4.1.x before 4.1.11, 4.2.x before 4.2.16, 4.3.x before 4.3.17 and 5.0.x before 5.0.8 have a hardcoded passphrase for the Fortimanager_Access account, which allows remote attackers to obtain administrative access via an SSH session.

Timeline

  1. First public exploit (Metasploit auxiliary/scanner/ssh/fortinet_backdoor)
  2. Published

Exploit prediction

71.27% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit auxiliary/scanner/ssh/fortinet_backdoor Fortinet SSH Backdoor Scanner metasploit auxiliary, normal rank, 2016-01-09
  • EDB-43386 Fortinet FortiGate 4.x < 5.0.7 - SSH Backdoor Access remote, 2016-01-09
  • exploit-db.com https://www.exploit-db.com/exploits/39224/ referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2016/Jan/26 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/135225/FortiGate-OS-5.0.7-SSH-Backdoor.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.