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

> Remote attackers can execute arbitrary PHP code via multiple parameters in the add_go.php script of WM-News.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6m2x-p5fv-h9gh

## What is CVE-2006-4768?

CVE-2006-4768 is a medium-severity code injection vulnerability in n/a, published on 13 Sep 2006. It can be exploited over the network, with no action from the victim.

### Official description

Multiple direct static code injection vulnerabilities in add_go.php in Stefan Ernst Newsscript (aka WM-News) 0.5 beta allow remote attackers to execute arbitrary PHP code via the (1) description, (2) issue, (3) title, (4) var, (5) name, (6) keywords, and (7) note parameters, which are stored in an article file.  NOTE: the original source of this vulnerability is unknown; the details are obtained from third party information and CVE post-disclosure analysis.

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

It affects 1 product.


Products: Stefan Ernst Newsscript.

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

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

## Is CVE-2006-4768 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4666](https://insights.sbomify.com/CVE-2006-4666/): Code injection in n/a (high 7.5)
- [CVE-2006-4767](https://insights.sbomify.com/CVE-2006-4767/): Path traversal in n/a (medium 6.4)
- [CVE-2006-4766](https://insights.sbomify.com/CVE-2006-4766/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4768 is a medium-severity code injection vulnerability in n/a, published on 13 Sep 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4768 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-2006-4768/ (Markdown: https://insights.sbomify.com/CVE-2006-4768/index.md)
```

## Sources

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

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