# CVE-2009-3922: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to delete user protection or bypass rules via CSRF in the Drupal User Protect module.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Nov 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qr4g-fwv9-54fx

## What is CVE-2009-3922?

CVE-2009-3922 is a medium-severity vulnerability in n/a, published on 9 Nov 2009. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in the User Protect module 5.x before 5.x-1.4 and 6.x before 6.x-1.3, a module for Drupal, allow remote attackers to hijack the authentication of administrators for requests that (1) delete the editing protection of a user or (2) delete a certain type of administrative-bypass rule.

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

## Which versions are affected by CVE-2009-3922?

It affects 1 product.


Products: Chad Phillips Userprotect.

## How do I fix CVE-2009-3922?

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

## Is CVE-2009-3922 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3922 and fix it if it is affected.

What it is: CVE-2009-3922 is a medium-severity vulnerability in n/a, published on 9 Nov 2009. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-3922 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-2009-3922/ (Markdown: https://insights.sbomify.com/CVE-2009-3922/index.md)
```

## Sources

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

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