# CVE-2007-4387: Cross-site request forgery in n/a

> Remote attackers can trick administrators into performing unauthorized configuration changes on 2wire Gateway routers via CSRF.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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:** 17 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j7cr-pfx5-wv5h

## What is CVE-2007-4387?

CVE-2007-4387 is a medium-severity vulnerability in n/a, published on 17 Aug 2007. 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 /xslt in 2wire 1701HG and 2071 Gateway routers, with 3.17.5 and 5.29.51 software, allows remote attackers to perform certain configuration changes as administrators.

## Which versions are affected by CVE-2007-4387?

It affects 2 products.


Products: 2wire 1701hg Router, 2wire 2071 Router.

## How do I fix CVE-2007-4387?

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

## Is CVE-2007-4387 being exploited?

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

Public exploit code:

- 2Wire Cross-Site Request Forgery Password Reset Vulnerability (metasploit)

## Other vulnerabilities in n/a

- [CVE-2007-4388](https://insights.sbomify.com/CVE-2007-4388/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2007-4389](https://insights.sbomify.com/CVE-2007-4389/): Cross-site request forgery in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4387 and fix it if it is affected.

What it is: CVE-2007-4387 is a medium-severity vulnerability in n/a, published on 17 Aug 2007. 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-2007-4387 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-2007-4387/ (Markdown: https://insights.sbomify.com/CVE-2007-4387/index.md)
```

## Sources

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

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