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

> Authenticated admins can execute arbitrary PHP code by uploading files with blocked extensions like .phtml due to insufficient validation.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rx39-82vr-xg3p

## What is CVE-2017-11715?

CVE-2017-11715 is a critical vulnerability in n/a, published on 28 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

job/uploadfile_save.php in MetInfo through 5.3.17 blocks the .php extension but not related extensions, which might allow remote authenticated admins to execute arbitrary PHP code by uploading a .phtml file after certain actions involving admin/system/safe.php and job/cv.php.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Metinfo Project Metinfo.

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

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

## Is CVE-2017-11715 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11717](https://insights.sbomify.com/CVE-2017-11717/): Security feature bypass in n/a (high 7.5)
- [CVE-2017-11716](https://insights.sbomify.com/CVE-2017-11716/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-11718](https://insights.sbomify.com/CVE-2017-11718/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11715 is a critical vulnerability in n/a, published on 28 Jul 2017. 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-2017-11715 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-11715/ (Markdown: https://insights.sbomify.com/CVE-2017-11715/index.md)
```

## Sources

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

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