# CVE-2021-22847: Hyweb HyCMS-J1 - SQL Injection

> Remote attackers can inject SQL commands via unfiltered POST parameters in Hyweb HyCMS-J1, allowing unauthorized data access and modification.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2hjx-vpw3-qh3w

## What is CVE-2021-22847?

CVE-2021-22847 is a high-severity SQL injection vulnerability in Hyweb HyCMS-J1, published on 22 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hyweb HyCMS-J1's API fail to filter POST request parameters. Remote attackers can inject SQL syntax and execute commands without privilege.

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

## Which versions are affected by CVE-2021-22847?

It affects 1 product.


Products: Hyweb Hycms-J1.

## How do I fix CVE-2021-22847?

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

## Is CVE-2021-22847 being exploited?

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

## Other vulnerabilities in Hyweb HyCMS-J1

- [CVE-2021-22849](https://insights.sbomify.com/CVE-2021-22849/): Hyweb HyCMS-J1 - Stored XSS (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22847 and fix it if it is affected.

What it is: CVE-2021-22847 is a high-severity SQL injection vulnerability in Hyweb HyCMS-J1, published on 22 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22847 in the wild and no public exploit code.

Affected product: Hyweb HyCMS-J1. 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-2021-22847/ (Markdown: https://insights.sbomify.com/CVE-2021-22847/index.md)
```

## Sources

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

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