# CVE-2017-11756: File upload in n/a

> Authenticated attackers can execute arbitrary PHP code by modifying upload settings to allow PHP files and uploading them via the music add feature.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wc6j-4h3g-8crj

## What is CVE-2017-11756?

CVE-2017-11756 is a high-severity vulnerability in n/a, published on 30 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Earcms Ear Music through 4.1 build 20170710, remote authenticated users can execute arbitrary PHP code by changing the allowable music-upload extensions to include .php in addition to .mp3 and .m4a in admin.php?iframe=config_upload, and then using user.php/music/add/ to upload the code.

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

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

It affects 1 product.


Products: Earcms Ear Music.

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

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

## Is CVE-2017-11756 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11756 is a high-severity vulnerability in n/a, published on 30 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11756 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-11756/ (Markdown: https://insights.sbomify.com/CVE-2017-11756/index.md)
```

## Sources

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

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