# CVE-2022-4015: Sports Club Management System make_payments.php sql injection

> Remote attackers can exploit SQL injection in the payment module to read or modify database contents.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5cwr-jjvf-gf39

## What is CVE-2022-4015?

CVE-2022-4015 is a medium-severity SQL injection vulnerability in unspecified Sports Club Management System, published on 16 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in Sports Club Management System 119. This affects an unknown part of the file admin/make_payments.php. The manipulation of the argument m_id/plan leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-213789 was assigned to this vulnerability.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-707 (Improper Neutralization)

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

It affects 1 product.


Products: Sports Club Management System Project Sports Club Management System.

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

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

## Is CVE-2022-4015 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4015 is a medium-severity SQL injection vulnerability in unspecified Sports Club Management System, published on 16 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4015 in the wild and no public exploit code.

Affected product: unspecified Sports Club Management System. 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-4015/ (Markdown: https://insights.sbomify.com/CVE-2022-4015/index.md)
```

## Sources

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

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