# CVE-2015-3613: Privilege escalation in n/a

> Attackers can escalate privileges via the WebUI FTP backup page in FortiManager, requiring an upgrade to secure the network management system.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fvxj-5jcm-7895

## What is CVE-2015-3613?

CVE-2015-3613 is a critical vulnerability in Fortinet Fortimanager, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in in FortiManager 5.2.1 and earlier and 5.0.10 and earlier in the WebUI FTP backup page

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2015-3613?

It affects 1 product.


Products: Fortinet Fortimanager.

## How do I fix CVE-2015-3613?

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

## Is CVE-2015-3613 being exploited?

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

## Other vulnerabilities in Fortinet Fortimanager

- [CVE-2024-47575](https://insights.sbomify.com/CVE-2024-47575/): Fortinet FortiManager Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2019-6695](https://insights.sbomify.com/CVE-2019-6695/): Security feature bypass in Fortinet FortiManager (critical 9.8)
- [CVE-2019-17654](https://insights.sbomify.com/CVE-2019-17654/): Cross-site request forgery in Fortinet FortiManager (high 8.8)
- [CVE-2015-3611](https://insights.sbomify.com/CVE-2015-3611/): Command injection in n/a (high 8.8)
- [CVE-2023-42791](https://insights.sbomify.com/CVE-2023-42791/): Path traversal in FortiAnalyzer (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3613 and fix it if it is affected.

What it is: CVE-2015-3613 is a critical vulnerability in Fortinet Fortimanager, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3613 in the wild and no public exploit code.

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

## Sources

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

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