# CVE-2013-3095: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to change passwords or enable remote management via CSRF in D-Link DIR865L routers.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Nov 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-g4jh-rqrc-rm99

## What is CVE-2013-3095?

CVE-2013-3095 is a medium-severity vulnerability in n/a, published on 19 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in D-Link DIR865L router (Rev. A1) with firmware before 1.05b07 allow remote attackers to hijack the authentication of administrators for requests that (1) change the administrator password or (2) enable remote management via a request to hedwig.cgi or (3) activate configuration changes via a request to pigwidgeon.cgi.

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

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

It affects 2 products.


Products: Dlink Dir865l, Dlink Dir865l Firmware.

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

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

## Is CVE-2013-3095 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3095 exists.

Public exploit code:

- D-Link DIR-865L - Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3095 is a medium-severity vulnerability in n/a, published on 19 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3095 exists.

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-3095/ (Markdown: https://insights.sbomify.com/CVE-2013-3095/index.md)
```

## Sources

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

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