# CVE-2006-3939: Missing authorization in n/a

> Remote attackers can perform administrative actions and upload arbitrary files without authentication due to missing authorization checks in ScriptsCenter ezUpload Pro.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2cwf-mxq6-x2pg

## What is CVE-2006-3939?

CVE-2006-3939 is a high-severity missing authorization vulnerability in n/a, published on 31 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ScriptsCenter ezUpload Pro 2.2.0 allows remote attackers to perform administrative activities without authentication in (1) filter.php, which permits changing the Extensions Mode file type; (2) access.php, which permits changing the Protection Method; (3) edituser.php, which permits adding upload capabilities to user accounts; (4) settings.php, which permits changing the admin information; and (5) index.php, which permits uploading of arbitrary files.

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

It affects 1 product.


Products: Scriptscenter Ezupload Pro.

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

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

## Is CVE-2006-3939 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2694](https://insights.sbomify.com/CVE-2006-2694/): Code injection in n/a (high 7.5)
- [CVE-2005-4308](https://insights.sbomify.com/CVE-2005-4308/): Path traversal in n/a (high 7.5)
- [CVE-2005-4309](https://insights.sbomify.com/CVE-2005-4309/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3939 is a high-severity missing authorization vulnerability in n/a, published on 31 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3939 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-3939/ (Markdown: https://insights.sbomify.com/CVE-2006-3939/index.md)
```

## Sources

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

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