# CVE-2013-7052: Auth bypass in n/a

> An attacker can bypass security controls on D-Link DIR-100 routers via a flaw in the cliget.cgi script.

- **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-p57j-9mpq-mpx6

## What is CVE-2013-7052?

CVE-2013-7052 is a critical authentication bypass vulnerability in n/a, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DIR-100 4.03B07: security bypass via an error in the cliget.cgi script

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Dlink Dir-100 Firmware.

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

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

## Is CVE-2013-7052 being exploited?

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

Public exploit code:

- D-Link DIR-100 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-7055](https://insights.sbomify.com/CVE-2013-7055/): Information disclosure in n/a (critical 9.8)
- [CVE-2013-7051](https://insights.sbomify.com/CVE-2013-7051/): Auth bypass in n/a (high 8.8)
- [CVE-2013-7053](https://insights.sbomify.com/CVE-2013-7053/): D-Link DIR-100 4.03B07: cli.cgi CSRF (high 8.8)
- [CVE-2013-7054](https://insights.sbomify.com/CVE-2013-7054/): D-Link DIR-100 4.03B07: cli.cgi XSS (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7052 is a critical authentication bypass vulnerability in n/a, 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-2013-7052 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-7052/ (Markdown: https://insights.sbomify.com/CVE-2013-7052/index.md)
```

## Sources

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

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