# CVE-2022-28093: File upload in n/a

> Attackers can execute arbitrary code by uploading a crafted PHP file to the SCBS Online Sports Venue Reservation System.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 25 Apr 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-vpw5-94jh-q7jg

## What is CVE-2022-28093?

CVE-2022-28093 is a critical vulnerability in n/a, published on 25 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SCBS Online Sports Venue Reservation System v1.0 was discovered to contain a local file inclusion vulnerability which allow attackers to execute arbitrary code via a crafted PHP file.

## Which versions are affected by CVE-2022-28093?

It affects 1 product.


Products: Online Sports Complex Booking System Project Online Sports Complex Booking System.

## How do I fix CVE-2022-28093?

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

## Is CVE-2022-28093 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28105](https://insights.sbomify.com/CVE-2022-28105/): SQL injection in n/a (critical 9.8)
- [CVE-2022-28106](https://insights.sbomify.com/CVE-2022-28106/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-28962](https://insights.sbomify.com/CVE-2022-28962/): SQL injection in n/a (critical 9.8)
- [CVE-2022-29985](https://insights.sbomify.com/CVE-2022-29985/): SQL injection in n/a (critical 9.8)
- [CVE-2022-29986](https://insights.sbomify.com/CVE-2022-29986/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28093 and fix it if it is affected.

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

## Sources

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

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