# CVE-2013-6990: Privilege escalation in n/a

> Remote administrators can escalate privileges via the command line interface in FortiAuthenticator, requiring an upgrade to secure the system.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vxhj-hm67-fv2j

## What is CVE-2013-6990?

CVE-2013-6990 is a critical vulnerability in n/a, published on 30 Apr 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

FortiGuard FortiAuthenticator before 3.0 allows remote administrators to gain privileges via the command line interface.

Weakness: CWE-264

## Which versions are affected by CVE-2013-6990?

It affects 1 product.


Products: Fortinet Fortiauthenticator.

## How do I fix CVE-2013-6990?

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

## Is CVE-2013-6990 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-44277](https://insights.sbomify.com/CVE-2026-44277/): Missing authorization in FortiAuthenticator (critical 9.1)
- [CVE-2021-43067](https://insights.sbomify.com/CVE-2021-43067/): Information disclosure in Fortinet FortiAuthenticator (high 8.3)
- [CVE-2021-22124](https://insights.sbomify.com/CVE-2021-22124/): Denial of service in Fortinet FortiSandbox, FortiAuthenticator (high 7.5)
- [CVE-2015-1455](https://insights.sbomify.com/CVE-2015-1455/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2025-53379](https://insights.sbomify.com/CVE-2025-53379/): Information disclosure in FortiAuthenticator (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6990 and fix it if it is affected.

What it is: CVE-2013-6990 is a critical vulnerability in n/a, published on 30 Apr 2014. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6990 in the wild and no public exploit code.

Affected product: n/a. 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-2013-6990/ (Markdown: https://insights.sbomify.com/CVE-2013-6990/index.md)
```

## Sources

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

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