# CVE-2018-13382: Fortinet FortiOS and FortiProxy Improper Authorization

> Unauthenticated attackers can modify SSL VPN user passwords via crafted HTTP requests, leading to account takeover.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 10 Jan 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-chg2-j3mj-m3rj

## What is CVE-2018-13382?

CVE-2018-13382 is a critical missing authorization vulnerability in Fortinet Fortios, published on 4 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Improper Authorization vulnerability in Fortinet FortiOS 6.0.0 to 6.0.4, 5.6.0 to 5.6.8 and 5.4.1 to 5.4.10 and FortiProxy 2.0.0, 1.2.0 to 1.2.8, 1.1.0 to 1.1.6, 1.0.0 to 1.0.7 under SSL VPN web portal allows an unauthenticated attacker to modify the password of an SSL VPN web portal user via specially crafted HTTP requests

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2018-13382?

It affects 2 products.


Products: Fortinet Fortios, Fortinet Fortiproxy.

## How do I fix CVE-2018-13382?

No fix has been published for CVE-2018-13382 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Jul 2022.

## Is CVE-2018-13382 being exploited?

Yes. Attackers have exploited CVE-2018-13382 in the wild since at least 10 Jan 2022, including in ransomware campaigns.

Public exploit code:

- CVE-2018-13382 (github_poc): https://github.com/milo2012/CVE-2018-13382
- PoC for CVE-2018-13382, never successfully tested so swim at your own risk (github_poc): https://github.com/tumikoto/Exploit-FortinetMagicBackdoor
- Fortinet FortiOS 6.0.4 - Unauthenticated SSL VPN User Password Modification (exploitdb)
- https://github.com/cojoben/CVE-2018-13382 (github_poc): https://github.com/cojoben/CVE-2018-13382

## Other vulnerabilities in Fortinet Fortios

- [CVE-2024-23113](https://insights.sbomify.com/CVE-2024-23113/): Fortinet Multiple Products Format String (critical 9.8, exploited in the wild)
- [CVE-2022-40684](https://insights.sbomify.com/CVE-2022-40684/): Fortinet Multiple Products Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-55591](https://insights.sbomify.com/CVE-2024-55591/): Fortinet FortiOS and FortiProxy Authentication Bypass (critical 9.6, exploited in the wild)
- [CVE-2024-21762](https://insights.sbomify.com/CVE-2024-21762/): Fortinet FortiOS Out-of-Bound Write (critical 9.6, exploited in the wild)
- [CVE-2022-42475](https://insights.sbomify.com/CVE-2022-42475/): Fortinet FortiOS Heap-Based Buffer Overflow (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-13382 and fix it if it is affected.

What it is: CVE-2018-13382 is a critical missing authorization vulnerability in Fortinet Fortios, published on 4 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-13382 in the wild since at least 10 Jan 2022, including in ransomware campaigns.

Affected product: Fortinet Fortios. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-13382/ (Markdown: https://insights.sbomify.com/CVE-2018-13382/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-13382
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-13382
- OSV: https://osv.dev/vulnerability/CVE-2018-13382

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-13382/
Summaries are generated and may contain mistakes; the official description above is the record.