# CVE-2016-7809: Cross-site request forgery in CG-WLR300NX

> Remote attackers can hijack authenticated sessions on Corega CG-WLR300NX routers to perform unintended operations via CSRF.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-354w-pm9c-w8rh

## What is CVE-2016-7809?

CVE-2016-7809 is a high-severity vulnerability in Corega Inc CG-WLR300NX, published on 9 Jun 2017. 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

Cross-site request forgery (CSRF) vulnerability in Corega CG-WLR300NX firmware Ver. 1.20 and earlier allows remote attackers to hijack the authentication of logged in user to conduct unintended operations via unspecified vectors.

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

## Which versions are affected by CVE-2016-7809?

It affects 1 product.


Products: Corega Cg-Wlr300nx Firmware.

## How do I fix CVE-2016-7809?

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

## Is CVE-2016-7809 being exploited?

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

## Other vulnerabilities in Corega Inc CG-WLR300NX

- [CVE-2016-7811](https://insights.sbomify.com/CVE-2016-7811/): Auth bypass in CG-WLR300NX (high 8.8)
- [CVE-2016-7810](https://insights.sbomify.com/CVE-2016-7810/): Cross-site scripting in CG-WLR300NX (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7809 and fix it if it is affected.

What it is: CVE-2016-7809 is a high-severity vulnerability in Corega Inc CG-WLR300NX, published on 9 Jun 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-7809 in the wild and no public exploit code.

Affected product: Corega Inc CG-WLR300NX. 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-2016-7809/ (Markdown: https://insights.sbomify.com/CVE-2016-7809/index.md)
```

## Sources

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

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