# CVE-2008-6690: Missing authorization in n/a

> Remote attackers can modify the configuration of the TYPO3 antispam plugin due to unspecified vulnerabilities.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 10 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-68g4-5vhp-p85w

## What is CVE-2008-6690?

CVE-2008-6690 is a high-severity missing authorization vulnerability in n/a, published on 10 Apr 2009. It can be exploited over the network.

### Official description

Unspecified vulnerability in nepa-design.de Spam Protection (nd_antispam) extension 1.0.3 for TYPO3 allows remote attackers to modify configuration via unknown vectors.

## Which versions are affected by CVE-2008-6690?

It affects 1 product.


Products: Typo3 Nd Antispam.

## How do I fix CVE-2008-6690?

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

## Is CVE-2008-6690 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6690 and fix it if it is affected.

What it is: CVE-2008-6690 is a high-severity missing authorization vulnerability in n/a, published on 10 Apr 2009. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2008-6690 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-2008-6690/ (Markdown: https://insights.sbomify.com/CVE-2008-6690/index.md)
```

## Sources

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

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