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

> Remote attackers can perform cross-site request forgery attacks against the Drupal module, bypassing security controls.

- **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:** No
- **Published:** 12 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-59rc-h7fv-6xfv

## What is CVE-2007-6320?

CVE-2007-6320 is a medium-severity vulnerability in n/a, published on 12 Dec 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Feature 4.7.x-dev and 5.x-dev before 20071206, a Drupal module, does not follow Drupal's Forms API submission model, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks.

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

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

It affects 1 product.


Products: Drupal Feature Module.

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

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

## Is CVE-2007-6320 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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