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

> Attackers can exploit SQL injection in Seecms to read or modify database contents, requiring immediate attention from CMS administrators.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2024
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-7453-c947-w47g

## What is CVE-2024-53502?

CVE-2024-53502 is a low-severity SQL injection vulnerability in Sem-Cms Semcms, published on 3 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Seecms v4.8 was discovered to contain a SQL injection vulnerability in the SEMCMS_SeoAndTag.php page.

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

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

It affects 1 product.


Products: Sem-Cms Semcms.

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

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

## Is CVE-2024-53502 being exploited?

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

## Other vulnerabilities in Sem-Cms Semcms

- [CVE-2025-25686](https://insights.sbomify.com/CVE-2025-25686/): SQL injection in n/a (critical 9.8)
- [CVE-2024-46103](https://insights.sbomify.com/CVE-2024-46103/): SQL injection in n/a (critical 9.8)
- [CVE-2024-30938](https://insights.sbomify.com/CVE-2024-30938/): SQL injection in n/a (critical 9.8)
- [CVE-2024-31012](https://insights.sbomify.com/CVE-2024-31012/): File upload in n/a (critical 9.8)
- [CVE-2024-25422](https://insights.sbomify.com/CVE-2024-25422/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53502 is a low-severity SQL injection vulnerability in Sem-Cms Semcms, published on 3 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53502 in the wild and no public exploit code.

Affected product: Sem-Cms Semcms. 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-53502/ (Markdown: https://insights.sbomify.com/CVE-2024-53502/index.md)
```

## Sources

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

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