CVE-2018-13374: A Improper Access Control in Fortinet FortiOS 6.0.2, 5.6.7 and before, FortiADC 6.1.0, 6.0.0 to 6.0.1, 5.4.0 to 5.4.4 allows attacker to…
Noroxi assessment
Priority: Plan (action score 58/100)
- CISA has confirmed exploitation in the wild (Sep 8, 2022); it is known to be used in ransomware campaigns. Remediation deadline for US federal agencies: Sep 29, 2022.
- Probability of exploitation in the next 30 days: 38% (FIRST EPSS); higher than 98.5% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
A Improper Access Control in Fortinet FortiOS 6.0.2, 5.6.7 and before, FortiADC 6.1.0, 6.0.0 to 6.0.1, 5.4.0 to 5.4.4 allows attacker to obtain the LDAP server login credentials configured in FortiGate via pointing a LDAP server connectivity test request to a rogue LDAP server instead of the configured one.
- Published
- Jan 22, 2019
- Updated
- Oct 1, 2026
- EPSS
- 38.0% · 98th percentile
- CWE
- CWE-732
Report tools
Action score
58
Add it to your regular patch cycle.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 11 / 30 · 38.0%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.3
- CNA · fortinet
- 4.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Sep 8, 2022. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Sep 29, 2022.
Known to be used in ransomware campaigns.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| fortinet | fortiadc | cpe:2.3:a:fortinet:fortiadc |
| fortinet | fortios | cpe:2.3:o:fortinet:fortios |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (fortinet). Independent of NVD's CPE analysis and usually ahead of it.
Fortinet Fortinet FortiOS, fortiADC
- FortiOS 6.0.2, 5.6.7 and before, FortiADC 6.1.0, 6.0.0 to 6.0.1, 5.4.0 to 5.4.4affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fortinet fortiadc5.4.0 and later · before 5.4.5
- fortinet fortiadc6.0.0 and later · before 6.0.2
- fortinet fortiadc6.1.0
- fortinet fortiosbefore 6.0.3
Same product
fortinet: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-38381An improper handling of malformed request vulnerability [CWE-228] exists in FortiADC 5.0 all versions, 6.0.0 all versions, 6.1.0 all…39Monitor
- CVE-2023-25603A permissive cross-domain policy with untrusted domains vulnerability in Fortinet FortiADC 7.1.0 - 7.1.1, FortiDDoS-F 6.3.0 - 6.3.4 and 6.4.36Monitor
- CVE-2022-39947A improper neutralization of special elements used in an os command ('os command injection') in Fortinet FortiADC version 7.0.0 through 7.0.36Monitor
Published before and after this one in the same product
- Later →CVE-2019-6699Mar 13, 2020 · An improper neutralization of input vulnerability in Fortinet FortiADC 5.3.3 and earlier may allow an attacker to execute a stored Cross…21Monitor
- Later →CVE-2021-24024Apr 12, 2021 · A clear text storage of sensitive information into log file vulnerability in FortiADCManager 5.3.0 and below, 5.2.1 and below and FortiADC…26Monitor
- Later →CVE-2020-15935Nov 2, 2021 · A cleartext storage of sensitive information in GUI in FortiADC versions 5.4.3 and below, 6.0.0 and below may allow a remote authenticated…17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2019-01-16 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-03-27 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-7 d
- Published
- CISA KEV+1324 d
- TodayNov 16, 2026+2855 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-732 · Incorrect Permission Assignment for Critical ResourceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Privilege AbuseCAPEC-122likelihood: High · Medium
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Exploiting Incorrectly Configured Access Control Security LevelsCAPEC-180likelihood: High · Medium
- Signing Malicious CodeCAPEC-206Very High
- Hijacking a privileged processCAPEC-234Medium
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- File and Directory DiscoveryT1083
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Server Software Component: Terminal Services DLLT1505.005
- Abuse Elevation Control MechanismT1548
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls:Code SigningT1553.002
- Compromise Client Software BinaryT1554
- Hijack Execution Flow:Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.