# CVE-2006-2695: File upload in n/a

> Remote attackers with admin access can execute arbitrary code by uploading malicious scripts to the image directory in DGNews.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/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:** 31 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wc7m-xwwq-3w4w

## What is CVE-2006-2695?

CVE-2006-2695 is a medium-severity vulnerability in n/a, published on 31 May 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

admin/upprocess.php in DGNews 1.5 and earlier allows remote attackers to execute arbitrary code by uploading scripts with arbitrary extensions to the img directory.

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

It affects 1 product.


Products: Dgnews Dgnews.

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

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

## Is CVE-2006-2695 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0692](https://insights.sbomify.com/CVE-2007-0692/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2695 is a medium-severity vulnerability in n/a, published on 31 May 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2695 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-2695/ (Markdown: https://insights.sbomify.com/CVE-2006-2695/index.md)
```

## Sources

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

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