# CVE-2014-9619: File upload in n/a

> Authenticated administrators can execute arbitrary PHP code by uploading malicious files with double extensions to the Netsweeper web console.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5872-pq3f-qqmv

## What is CVE-2014-9619?

CVE-2014-9619 is a high-severity vulnerability in n/a, published on 19 Sep 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in webadmin/ajaxfilemanager/ajaxfilemanager.php in Netsweeper before 3.1.10, 4.0.x before 4.0.9, and 4.1.x before 4.1.2 allows remote authenticated users with admin privileges on the Cloud Manager web console to execute arbitrary PHP code by uploading a file with a double extension, then accessing it via a direct request to the file in webadmin/deny/images/, as demonstrated by secuid0.php.gif.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2014-9619?

It affects 1 product.


Products: Netsweeper Netsweeper.

## How do I fix CVE-2014-9619?

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

## Is CVE-2014-9619 being exploited?

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

Public exploit code:

- Netsweeper 4.0.8 - Arbitrary File Upload / Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-3859](https://insights.sbomify.com/CVE-2012-3859/): Other in n/a (critical 10.0)
- [CVE-2020-13167](https://insights.sbomify.com/CVE-2020-13167/): Command injection in n/a (critical 9.8)
- [CVE-2014-9612](https://insights.sbomify.com/CVE-2014-9612/): SQL injection in n/a (critical 9.8)
- [CVE-2014-9613](https://insights.sbomify.com/CVE-2014-9613/): SQL injection in n/a (critical 9.8)
- [CVE-2014-9614](https://insights.sbomify.com/CVE-2014-9614/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9619 and fix it if it is affected.

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

## Sources

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

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