# CVE-2008-6823: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to modify network settings and credentials via CSRF in A-LINK access points.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 4 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5x6q-3q26-2rq9

## What is CVE-2008-6823?

CVE-2008-6823 is a medium-severity vulnerability in n/a, published on 4 Jun 2009. 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 in the management interface on the A-LINK WL54AP3 and WL54AP2 access points before firmware 1.4.2-eng1 allow remote attackers to hijack the authentication of administrators for requests that (1) modify the network configuration via certain parameters to goform/formWanTcpipSetup or (2) modify credentials via certain parameters to goform/formPasswordSetup.

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

## Which versions are affected by CVE-2008-6823?

It affects 2 products.


Products: A-Link Wl54ap2, A-Link Wl54ap3.

## How do I fix CVE-2008-6823?

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

## Is CVE-2008-6823 being exploited?

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

Public exploit code:

- A-Link WL54AP3 / WL54AP2 - Cross-Site Request Forgery / Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6824](https://insights.sbomify.com/CVE-2008-6824/): Hardcoded credentials in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6823 and fix it if it is affected.

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

## Sources

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

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