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

> Remote attackers can trick administrators into performing unauthorized actions via CSRF in Drupal localization modules, leading to privilege escalation.

- **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:** 19 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6398-vm89-wp76

## What is CVE-2008-6169?

CVE-2008-6169 is a medium-severity vulnerability in n/a, published on 19 Feb 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

Cross-site request forgery (CSRF) vulnerability in the Localization client 5.x before 5.x-1.1 and 6.x before 6.x-1.6 and the Localization server 5.x before 5.x-1.0-alpha5 and 6.x before 6.x-alpha2, modules for Drupal, allows remote attackers to perform unauthorized actions as administrators via unspecified vectors related to the "local translation submission interface."

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

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

It affects 2 products.


Products: Drupal Localization Client, Drupal Localization Server.

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

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

## Is CVE-2008-6169 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1344](https://insights.sbomify.com/CVE-2009-1344/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6169 is a medium-severity vulnerability in n/a, published on 19 Feb 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: There is no known exploitation of CVE-2008-6169 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-2008-6169/ (Markdown: https://insights.sbomify.com/CVE-2008-6169/index.md)
```

## Sources

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

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