# CVE-2023-5185: Gym Management System Project v1.0 - Insecure File Upload

> An authenticated attacker can upload malicious files to achieve remote code execution on the server hosting the Gym Management System.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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:** 28 Sep 2023
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-jv2q-4pxc-v47p

## What is CVE-2023-5185?

CVE-2023-5185 is a critical vulnerability in Gym Management System Project, published on 28 Sep 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Gym Management System Project v1.0 is vulnerable to

an Insecure File Upload vulnerability on the 'file'

parameter of profile/i.php page, allowing an

authenticated attacker to obtain Remote Code Execution

on the server hosting the application.

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

## Which versions are affected by CVE-2023-5185?

It affects 1 product.


Products: Projectworlds Gym Management System Project.

## How do I fix CVE-2023-5185?

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

## Is CVE-2023-5185 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5185 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5185 and fix it if it is affected.

What it is: CVE-2023-5185 is a critical vulnerability in Gym Management System Project, published on 28 Sep 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5185 exists.

Affected product: Gym Management System Project. 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-2023-5185/ (Markdown: https://insights.sbomify.com/CVE-2023-5185/index.md)
```

## Sources

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

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