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

> Students or teachers can upload arbitrary files in the school management system, potentially leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qrwq-jfp7-q2qg

## What is CVE-2017-15957?

CVE-2017-15957 is a high-severity vulnerability in n/a, published on 29 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

my_profile.php in Ingenious School Management System 2.3.0 allows a student or teacher to upload an arbitrary file.

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

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

It affects 1 product.


Products: Ingenious School Management System Project Ingenious School Management System.

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

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

## Is CVE-2017-15957 being exploited?

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

Public exploit code:

- Ingenious 2.3.0 - Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-16561](https://insights.sbomify.com/CVE-2017-16561/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15957 is a high-severity vulnerability in n/a, published on 29 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15957 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-15957/ (Markdown: https://insights.sbomify.com/CVE-2017-15957/index.md)
```

## Sources

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

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