# CVE-2017-12756: Command injection in n/a

> Attackers can execute arbitrary commands via the userfile parameter in extplorer, requiring immediate patching.

- **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:** Yes
- **Published:** 9 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DLA-1063-1, GHSA-c4wx-89j8-9hmm, UBUNTU-CVE-2017-12756

## What is CVE-2017-12756?

CVE-2017-12756 is a high-severity command injection vulnerability in n/a, published on 9 Aug 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Command inject in transfer from another server in extplorer 2.1.9 and prior allows attacker to inject command via the userfile[0] parameter.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2017-12756?

It affects 1 product.


Products: Extplorer Extplorer.

## How do I fix CVE-2017-12756?

Apply the vendor's patch.

## Is CVE-2017-12756 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6710](https://insights.sbomify.com/CVE-2012-6710/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-54335](https://insights.sbomify.com/CVE-2023-54335/): eXtplorer<= 2.1.14 - Authentication Bypass & Remote Code Execution (RCE) (critical 9.3)
- [CVE-2023-29657](https://insights.sbomify.com/CVE-2023-29657/): File upload in n/a (high 8.8)
- [CVE-2023-27842](https://insights.sbomify.com/CVE-2023-27842/): Missing authorization in n/a (high 8.8)
- [CVE-2016-4313](https://insights.sbomify.com/CVE-2016-4313/): Path traversal in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12756 and fix it if it is affected.

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

## Sources

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

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