# CVE-2016-4066: Cross-site request forgery (CSRF) vulnerability in Fortinet FortiWeb before 5.5.3 allows remote attackers to hijack the authentication of ad


- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Jul 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v572-2cxh-pm8p

## What is CVE-2016-4066?

CVE-2016-4066 is a high-severity vulnerability in Fortinet Fortiweb, published on 13 Jul 2016. 

### Official description

Cross-site request forgery (CSRF) vulnerability in Fortinet FortiWeb before 5.5.3 allows remote attackers to hijack the authentication of administrators for requests that change the password via unspecified vectors.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2016-4066?

It affects 1 product.


Products: Fortinet Fortiweb.

## How do I fix CVE-2016-4066?

No fix has been published for CVE-2016-4066 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-4066 being exploited?

There is no known exploitation of CVE-2016-4066 in the wild and no public exploit code.

## Other vulnerabilities in Fortinet Fortiweb

- [CVE-2025-25257](https://insights.sbomify.com/CVE-2025-25257/): Fortinet FortiWeb SQL Injection (critical 9.6, exploited in the wild)
- [CVE-2025-64446](https://insights.sbomify.com/CVE-2025-64446/): Fortinet FortiWeb Path Traversal (critical 9.4, exploited in the wild)
- [CVE-2025-58034](https://insights.sbomify.com/CVE-2025-58034/): Fortinet FortiWeb OS Command Injection (medium 6.7, exploited in the wild)
- [CVE-2020-29015](https://insights.sbomify.com/CVE-2020-29015/): SQL injection in Fortinet FortiWeb (critical 9.8)
- [CVE-2020-29016](https://insights.sbomify.com/CVE-2020-29016/): Memory corruption in Fortinet FortiWeb (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4066 and fix it if it is affected.

What it is: CVE-2016-4066 is a high-severity vulnerability in Fortinet Fortiweb, published on 13 Jul 2016. 
Exploitation: There is no known exploitation of CVE-2016-4066 in the wild and no public exploit code.

Affected product: Fortinet Fortiweb. 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-2016-4066/ (Markdown: https://insights.sbomify.com/CVE-2016-4066/index.md)
```

## Sources

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

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