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

> TestLink fails to enforce authorization, potentially allowing unauthorized access to functionality or data.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 15 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m978-2g9r-q8xc

## What is CVE-2007-6006?

CVE-2007-6006 is a critical missing authorization vulnerability in n/a, published on 15 Nov 2007. It can be exploited over the network.

### Official description

TestLink before 1.7.1 does not enforce an unspecified authorization mechanism, which has unknown impact and attack vectors.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Testlink Testlink.

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

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

## Is CVE-2007-6006 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12274](https://insights.sbomify.com/CVE-2020-12274/): Open redirect in n/a (critical 9.8)
- [CVE-2020-8637](https://insights.sbomify.com/CVE-2020-8637/): SQL injection in n/a (critical 9.8)
- [CVE-2020-8638](https://insights.sbomify.com/CVE-2020-8638/): SQL injection in n/a (critical 9.8)
- [CVE-2015-7390](https://insights.sbomify.com/CVE-2015-7390/): SQL injection in n/a (critical 9.8)
- [CVE-2014-5308](https://insights.sbomify.com/CVE-2014-5308/): SQL injection in n/a (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6006 is a critical missing authorization vulnerability in n/a, published on 15 Nov 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-6006 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-6006/ (Markdown: https://insights.sbomify.com/CVE-2007-6006/index.md)
```

## Sources

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

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