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

> Remote attackers can bypass authentication and modify router settings by sending a specific User-Agent header, affecting multiple D-Link, Planex, and Alpha Networks devices.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v2pf-28pq-8p67

## What is CVE-2013-6026?

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

### Official description

The web interface on D-Link DIR-100, DIR-120, DI-624S, DI-524UP, DI-604S, DI-604UP, DI-604+, and TM-G5240 routers; Planex BRL-04R, BRL-04UR, and BRL-04CW routers; and Alpha Networks routers allows remote attackers to bypass authentication and modify settings via an xmlset_roodkcableoj28840ybtide User-Agent HTTP header, as exploited in the wild in October 2013.

Weakness: CWE-264

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

It affects 13 products.


Products: Alphanetworks Vdsl Asl-55052, Alphanetworks Vdsl Asl-56552, Dlink Di-524up, Dlink Di-604\+, Dlink Di-604s, Dlink Di-604up, Dlink Di-624s, Dlink Dir-100, Dlink Dir-120, Dlink Tm-G5240, Planex Brl-04cw, Planex Brl-04r, Planex Brl-04ur.

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

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

## Is CVE-2013-6026 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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