CVE-2022-4961 is a medium severity SQL injection flaw in Weitong Mall 1.0.0, scored 5.5 by NVD. The sidx and order arguments reach a query in OrderDao.xml without safe handling. I could not confirm a fixed version, so check the project before relying on any release.
What's affected
The record says Weitong Mall 1.0.0 is affected through the file platform-shop/src/main/resources/com/platform/dao/OrderDao.xml, where manipulating the sidx or order argument leads to SQL injection. The record carries the identifier VDB-250243 and says it was declared critical in the report. The NVD vector is CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, which needs adjacent network access and a low privilege account and scores 5.5. The record also says the report declared it critical, so the two ratings differ.
The project's public issue, created in October 2022 on Gitee, says the reporter followed the call into the controller layer and confirmed in a debugger that the sidx value can be injected. The issue is marked as completed, but I could not see a linked change or a release, and the VulDB pages did not load. I therefore cannot name a fixed version.
The project is published as an open source shop platform. If you run it or a fork, treat the sorting parameters as unsafe until you have checked your own copy of the query.
Weakness class: CWE-89.
How to check if you're exposed
There is no package to query. Open your copy of the project and look at OrderDao.xml in the platform-shop module. If the file is a MyBatis style mapper, as its location suggests, a value written with a dollar sign and braces is pasted into the query as text, while a value written with a hash sign and braces is passed as a bound parameter. A sort column or sort order written the first way is the pattern the report describes.
Search other mapper files for the same style, since a sort field copied between files repeats the problem. For example:
grep -rn 'order by' --include=*.xml platform-shop/src/main/resources | head -50
Then check whether the application is reachable by people who should not use it, and whether the account it uses to talk to the database has more rights than it needs.
What to do now
- Find any deployments of Weitong Mall and note whether they are 1.0.0 or a fork.
- Check the project's repository for a fix, and apply it if one exists.
- If not, change the sorting code so the column and direction are chosen from a fixed list in code instead of taken from the request.
- Give the database account the fewest rights that the application needs.
- Add a web application firewall rule or input check as a stopgap, and monitor for odd sort parameters.
Why it matters
Sorting is a common place for injection because query builders cannot bind a column name or a sort direction as a parameter. Developers fall back to pasting the request value into the query, and any value then becomes part of the SQL. The record files it as CWE-89, improper neutralisation of special elements in an SQL command.
The right fix is an allowlist. Map the incoming names to known column names in code, and ignore anything else. Escaping is fragile, because the context is an identifier and not a string.
The report declared it critical, while NVD scores it 5.5 Medium, because the NVD vector needs adjacent network access and a low privilege account and rates the impact on each area as low. Which view fits depends on who can log in to your deployment and what the database holds.
This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is there a fix for CVE-2022-4961?
I could not confirm one. The public issue is marked completed but I saw no linked release, so check the project repository directly.
Why do the ratings differ?
The report declared it critical, while NVD scores 5.5 Medium based on a low privilege requirement and limited impact.
Sources
Last reviewed: 19 October 2026.