# CVE-2016-7454: Cross-site request forgery in n/a

> Attackers can exploit CSRF to change Wi-Fi passwords, enable remote management, or reset the router on affected Technicolor devices.

- **Severity:** High 8.0 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r2vc-j63m-w8mh

## What is CVE-2016-7454?

CVE-2016-7454 is a high-severity vulnerability in n/a, published on 17 Dec 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

CSRF vulnerability on Technicolor TC dpc3941T (formerly Cisco dpc3941T) devices with firmware dpc3941-P20-18-v303r20421733-160413a-CMCST allows an attacker to change the Wi-Fi password, open the remote management interface, or reset the router.

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

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

It affects 1 product.


Products: Technicolor Xfinity Gateway Router Dpc3941t Firmware.

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

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

## Is CVE-2016-7454 being exploited?

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

Public exploit code:

- Xfinity Gateway (Technicolor DPC3941T) - Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-7454 is a high-severity vulnerability in n/a, published on 17 Dec 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-7454 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-2016-7454/ (Markdown: https://insights.sbomify.com/CVE-2016-7454/index.md)
```

## Sources

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

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