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

> Remote attackers can hijack user sessions to modify account details via CSRF in PHPmotion.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** No
- **Published:** 20 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4244-mrv4-7597

## What is CVE-2008-6729?

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

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in password.php in PHPmotion 2.1 and earlier allow remote attackers to hijack the authentication of arbitrary users for requests that modify an account via the (1) password or (2) email_address parameter.

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

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

It affects 1 product.


Products: Phpmotion Phpmotion.

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

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

## Is CVE-2008-6729 being exploited?

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

Public exploit code:

- PHPmotion 2.1 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3118](https://insights.sbomify.com/CVE-2008-3118/): SQL injection in n/a (high 7.5)
- [CVE-2008-3117](https://insights.sbomify.com/CVE-2008-3117/): File upload in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6729 is a medium-severity vulnerability in n/a, published on 20 Apr 2009. Any signed-in user can exploit it over the network, 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-6729 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-6729/ (Markdown: https://insights.sbomify.com/CVE-2008-6729/index.md)
```

## Sources

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

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