# CVE-2022-4961: Weitong Mall OrderDao.xml sql injection

> SQL injection in Weitong Mall allows attackers to manipulate database queries via the sidx/order parameters, potentially exposing or altering data.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2024
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-jhv9-m2c5-2xm6

## What is CVE-2022-4961?

CVE-2022-4961 is a medium-severity SQL injection vulnerability in Weitong Mall, published on 12 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Weitong Mall 1.0.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file platform-shop\src\main\resources\com\platform\dao\OrderDao.xml. The manipulation of the argument sidx/order leads to sql injection. The associated identifier of this vulnerability is VDB-250243.

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

## Which versions are affected by CVE-2022-4961?

It affects 1 product.


Products: Fuyanglipengjun Wetong Mall.

## How do I fix CVE-2022-4961?

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

## Is CVE-2022-4961 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4961 and fix it if it is affected.

What it is: CVE-2022-4961 is a medium-severity SQL injection vulnerability in Weitong Mall, published on 12 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4961 in the wild and no public exploit code.

Affected product: Weitong Mall. 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-2022-4961/ (Markdown: https://insights.sbomify.com/CVE-2022-4961/index.md)
```

## Sources

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

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