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

> Remote attackers can perform administrative actions via CSRF, requiring user interaction to trigger malicious requests.

- **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:** 13 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w73f-pxm3-f825

## What is CVE-2007-6708?

CVE-2007-6708 is a medium-severity vulnerability in n/a, published on 13 Mar 2008. 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 Cisco Linksys WAG54GS Wireless-G ADSL Gateway with 1.01.03 and earlier firmware allow remote attackers to perform actions as administrators via an arbitrary valid request to an administrative URI, as demonstrated by (1) a Restore Factory Defaults action using the mtenRestore parameter to setup.cgi and (2) creation of a user account using the sysname parameter to setup.cgi.

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

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

It affects 1 product.


Products: Linksys Wag54gs.

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

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

## Is CVE-2007-6708 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6709](https://insights.sbomify.com/CVE-2007-6709/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2007-6707](https://insights.sbomify.com/CVE-2007-6707/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2007-3574](https://insights.sbomify.com/CVE-2007-3574/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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