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

> Remote attackers can modify user preferences and passwords via CSRF in Ikiwiki, requiring user interaction to exploit.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-0165, DSA-1553-1, GHSA-x687-7fxp-pcgf

## What is CVE-2008-0165?

CVE-2008-0165 is a medium-severity vulnerability in n/a, published on 20 Apr 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in Ikiwiki before 2.42 allows remote attackers to modify user preferences, including passwords, via the (1) preferences and (2) edit forms.

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

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

It affects 1 product.


Products: Ikiwiki Ikiwiki.

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

Upgrade to a fixed version.

## Is CVE-2008-0165 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9187](https://insights.sbomify.com/CVE-2019-9187/): Server-side request forgery in n/a (high 7.5)
- [CVE-2016-10026](https://insights.sbomify.com/CVE-2016-10026/): Missing authorization in n/a (high 7.5)
- [CVE-2008-0169](https://insights.sbomify.com/CVE-2008-0169/): Auth bypass in n/a (medium 6.8)
- [CVE-2016-9645](https://insights.sbomify.com/CVE-2016-9645/): Editing restriction bypass for git revert (medium 6.5)
- [CVE-2010-1673](https://insights.sbomify.com/CVE-2010-1673/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0165 is a medium-severity vulnerability in n/a, published on 20 Apr 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-0165 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-0165/ (Markdown: https://insights.sbomify.com/CVE-2008-0165/index.md)
```

## Sources

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

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