CVE-2026-8771
SQL Injection in Litemall WeChat API
Publication date: 2026-05-18
Last updated on: 2026-05-18
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linlinjava | litemall | to 1.8.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-8771 is a critical SQL injection vulnerability found in linlinjava litemall versions up to 1.8.0. It affects the front-end WeChat API, specifically the function list in the file WxGoodsController.java. The vulnerability arises because the 'sort' parameter is directly concatenated into an SQL ORDER BY clause without proper sanitization or validation.
This flaw allows attackers to perform SQL injection attacks remotely without needing admin authentication. Attackers can exploit this by manipulating the 'sort' parameter to inject malicious SQL commands, enabling various types of SQL injection such as error-based, boolean-based, and time-based blind SQL injection.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data. Exploits can extract admin password hashes, database version information, table names, and all user data, which may include personal information and payment details.
Because the vulnerability can be exploited remotely by any user without authentication, it poses a high risk of data breach, data loss, and potential compromise of the entire database.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the front-end API endpoint `/wx/goods/list` for SQL injection via the `sort` parameter. Since the parameter is directly concatenated into an SQL ORDER BY clause without sanitization, sending specially crafted payloads can reveal the vulnerability.
Common detection methods include error-based, boolean-based, and time-based blind SQL injection techniques targeting the `sort` parameter.
- Use curl or similar tools to send requests with SQL injection payloads in the `sort` parameter, for example: `curl 'http://target/wx/goods/list?sort=1'` and then try payloads like `sort=1 OR SLEEP(5)` to detect time delays.
- Use automated SQL injection detection tools such as sqlmap targeting the endpoint with the `sort` parameter to confirm the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves implementing strict whitelist validation for the `sort` and `order` parameters to prevent malicious input from being executed in SQL queries.
This can be done by using annotations like `@Sort` or server-side validation against a predefined list of allowed values, ensuring only safe sorting options are accepted.
Additionally, monitor and restrict access to the vulnerable endpoint and consider applying web application firewall (WAF) rules to block suspicious payloads targeting the `sort` parameter.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability allows attackers to extract sensitive data including personal information and payment details from the affected system.
Exposure of such sensitive data can lead to violations of data protection regulations such as GDPR and HIPAA, which mandate the protection of personal and payment information.
Therefore, exploitation of this vulnerability could result in non-compliance with these common standards and regulations due to unauthorized data disclosure.