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

> An attacker can inject SQL commands via the parentid parameter in the edit_post method to read or modify database content.

- **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:** 25 Oct 2024
- **Updated:** 29 Oct 2024
- **Also known as:** GHSA-fvm7-9wr5-2cgx

## What is CVE-2024-48238?

CVE-2024-48238 is a medium-severity SQL injection vulnerability in n/a, published on 25 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

WTCMS 1.0 is vulnerable to SQL Injection in the edit_post method of /Admin\Controller\NavControl.class.php via the parentid parameter.

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

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

It affects 1 product.


Products: Wtcms Project Wtcms.

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

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

## Is CVE-2024-48238 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-48237](https://insights.sbomify.com/CVE-2024-48237/): Missing authorization in n/a (critical 9.8)
- [CVE-2019-8908](https://insights.sbomify.com/CVE-2019-8908/): File upload in n/a (critical 9.8)
- [CVE-2019-8910](https://insights.sbomify.com/CVE-2019-8910/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-10267](https://insights.sbomify.com/CVE-2018-10267/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-8909](https://insights.sbomify.com/CVE-2019-8909/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48238 is a medium-severity SQL injection vulnerability in n/a, published on 25 Oct 2024. 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-2024-48238 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-48238/ (Markdown: https://insights.sbomify.com/CVE-2024-48238/index.md)
```

## Sources

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

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