# CVE-2007-3690: Missing authorization in n/a

> Remote attackers can read restricted posts in Drupal by modifying URL arguments, bypassing node access controls.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5r9m-522w-fg7m

## What is CVE-2007-3690?

CVE-2007-3690 is a high-severity missing authorization vulnerability in n/a, published on 11 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Forward module before 4.7-1.1 and 5.x before 5.x-1.0 for Drupal allows remote attackers to read restricted posts in (1) Organic Groups, (2) Taxonomy Access Control, (3) Taxonomy Access Lite, and other unspecified node access modules, via modified URL arguments.

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

It affects 1 product.


Products: Drupal Forward Module.

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

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

## Is CVE-2007-3690 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3690 is a high-severity missing authorization vulnerability in n/a, published on 11 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-3690 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-3690/ (Markdown: https://insights.sbomify.com/CVE-2007-3690/index.md)
```

## Sources

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

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