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

> Authenticated users can bypass access controls to read issue details and attached files by guessing filenames in the Drupal issue tracking module.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/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:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cgjv-226f-h6vj

## What is CVE-2007-0506?

CVE-2007-0506 is a medium-severity missing authorization vulnerability in n/a, published on 26 Jan 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The project_issue_access function in the Project issue tracking 4.7.0 through 5.x before 20070123 module for Drupal allows remote authenticated users to bypass other access control modules and obtain attached files by guessing the filename, and obtain issue information via direct requests.

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

It affects 2 products.


Products: Drupal Project, Drupal Project Issue Tracking Module.

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

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

## Is CVE-2007-0506 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0505](https://insights.sbomify.com/CVE-2007-0505/): File upload in n/a (high 8.5)
- [CVE-2007-4436](https://insights.sbomify.com/CVE-2007-4436/): Missing authorization in n/a (medium 5.0)
- [CVE-2007-0534](https://insights.sbomify.com/CVE-2007-0534/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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