# CVE-2024-46078: SQL injection in n/a

> An attacker can execute arbitrary SQL commands via the id parameter in the delete_category function, potentially reading or modifying database contents.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2024
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-mjg9-2fc5-7g27

## What is CVE-2024-46078?

CVE-2024-46078 is a high-severity SQL injection vulnerability in n/a, published on 4 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

itsourcecode Sports Management System Project 1.0 is vulnerable to SQL Injection in the function delete_category of the file sports_scheduling/player.php via the argument id.

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

## Which versions are affected by CVE-2024-46078?

It affects 1 product.


Products: Adonesevangelista Sports Management System.

## How do I fix CVE-2024-46078?

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

## Is CVE-2024-46078 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-46078 and fix it if it is affected.

What it is: CVE-2024-46078 is a high-severity SQL injection vulnerability in n/a, published on 4 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-46078 exists.

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-2024-46078/ (Markdown: https://insights.sbomify.com/CVE-2024-46078/index.md)
```

## Sources

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

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