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

> Remote attackers can hijack administrator sessions to modify FTP settings and bandwidth limits on TP-LINK WR1043N routers via CSRF.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qfvq-m4vm-x9px

## What is CVE-2013-2645?

CVE-2013-2645 is a critical vulnerability in n/a, published on 6 Oct 2014. 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 on the TP-LINK WR1043N router with firmware TL-WR1043ND_V1_120405 allow remote attackers to hijack the authentication of administrators for requests that (1) enable FTP access (aka "FTP directory traversal") to /tmp via the shareEntire parameter to userRpm/NasFtpCfgRpm.htm, (2) change the FTP administrative password via the nas_admin_pwd parameter to userRpm/NasUserAdvRpm.htm, (3) enable FTP on the WAN interface via the internetA parameter to userRpm/NasFtpCfgRpm.htm, (4) launch the FTP service via the startFtp parameter to userRpm/NasFtpCfgRpm.htm, or (5) enable or disable bandwidth limits via the QoSCtrl parameter to userRpm/QoSCfgRpm.htm.

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

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

It affects 1 product.


Products: Tp-Link Firmware.

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

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

## Is CVE-2013-2645 being exploited?

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

Public exploit code:

- TP-Link TL-WR1043N Router - Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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