# CVE-2006-6786: Code injection in n/a

> Authenticated administrators can execute arbitrary PHP code via the email parameter in Open Newsletter, requiring an upgrade to mitigate.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-624v-9wf2-xxfc

## What is CVE-2006-6786?

CVE-2006-6786 is a medium-severity code injection vulnerability in n/a, published on 28 Dec 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Open Newsletter 2.5 and earlier allows remote authenticated administrators to execute arbitrary PHP code by inserting the code into the email parameter to (1) subscribe.php or (2) unsubscribe.php.

## Which versions are affected by CVE-2006-6786?

It affects 1 product.


Products: Open Newsletter Open Newsletter.

## How do I fix CVE-2006-6786?

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

## Is CVE-2006-6786 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6786 exists.

Public exploit code:

- open NewsLetter 2.5 - Multiple Vulnerabilities (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6785](https://insights.sbomify.com/CVE-2006-6785/): Auth bypass in n/a (high 7.5)
- [CVE-2007-6301](https://insights.sbomify.com/CVE-2007-6301/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6786 and fix it if it is affected.

What it is: CVE-2006-6786 is a medium-severity code injection vulnerability in n/a, published on 28 Dec 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6786 exists.

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-2006-6786/ (Markdown: https://insights.sbomify.com/CVE-2006-6786/index.md)
```

## Sources

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

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