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

> Remote attackers can change arbitrary user passwords via CSRF in Django admin panel if CSRF protection is not enabled.

- **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:** Yes
- **Published:** 5 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5828, GHSA-pjc8-j97x-hp3p

## What is CVE-2007-5828?

CVE-2007-5828 is a medium-severity vulnerability in n/a, published on 5 Nov 2007. 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 admin panel in Django 0.96 allows remote attackers to change passwords of arbitrary users via a request to admin/auth/user/1/password/.  NOTE: this issue has been disputed by Debian, since product documentation includes a recommendation for a CSRF protection module that is included with the product.  However, CVE considers this an issue because the default configuration does not use this module

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

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

It affects 1 product.


Products: Django Project Django.

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

Change a configuration setting.

## Is CVE-2007-5828 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0404](https://insights.sbomify.com/CVE-2007-0404/): Django Arbitrary Code Execution (high 7.5)
- [CVE-2007-0405](https://insights.sbomify.com/CVE-2007-0405/): Django Improper Access Control (medium 6.5)
- [CVE-2009-2659](https://insights.sbomify.com/CVE-2009-2659/): Django Admin Media Handler Vulnerable to Directory Traversal (medium 5.0)
- [CVE-2008-2302](https://insights.sbomify.com/CVE-2008-2302/): Django Cross-site scripting (XSS) vulnerability (medium 4.3)
- [CVE-2007-5712](https://insights.sbomify.com/CVE-2007-5712/): Django vulnerable to Denial of Service via i18n middleware component (low 2.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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