# CVE-2020-22818: SQL injection in n/a

> An attacker can execute arbitrary SQL commands via the name parameter in the registration script, potentially accessing or modifying database contents.

- **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:** 3 Nov 2022
- **Updated:** 5 May 2025
- **Also known as:** GHSA-3f2r-h473-hqjx

## What is CVE-2020-22818?

CVE-2020-22818 is a critical SQL injection vulnerability in n/a, published on 3 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MKCMS V6.2 has SQL injection via /ucenter/reg.php name parameter.

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

## Which versions are affected by CVE-2020-22818?

It affects 1 product.


Products: Mkcms Project Mkcms.

## How do I fix CVE-2020-22818?

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

## Is CVE-2020-22818 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-22819](https://insights.sbomify.com/CVE-2020-22819/): SQL injection in n/a (critical 9.8)
- [CVE-2020-22820](https://insights.sbomify.com/CVE-2020-22820/): SQL injection in n/a (critical 9.8)
- [CVE-2019-10707](https://insights.sbomify.com/CVE-2019-10707/): SQL injection in n/a (critical 9.8)
- [CVE-2019-11332](https://insights.sbomify.com/CVE-2019-11332/): Business logic in n/a (high 8.8)
- [CVE-2019-11078](https://insights.sbomify.com/CVE-2019-11078/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-22818 and fix it if it is affected.

What it is: CVE-2020-22818 is a critical SQL injection vulnerability in n/a, published on 3 Nov 2022. 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-2020-22818 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-2020-22818/ (Markdown: https://insights.sbomify.com/CVE-2020-22818/index.md)
```

## Sources

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

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