linlinjava litemall up to 1.8.0 Admin Endpoint sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in linlinjava litemall up to 1.8.0. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component Admin Endpoint. The manipulation leads to sql injection. This vulnerability is uniquely identified as CVE-2026-8772. The attack is possible to be carried out remotely. Moreover, an exploit is present. Multiple endpoints are affected. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in linlinjava litemall up to 1.8.0 and classified as critical. This issue affects an unknown code block of the component Admin Endpoint. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.
The advisory is shared at gist.github.com. The identification of this vulnerability is CVE-2026-8772. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are required for exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The exploit is available at gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way. Multiple endpoints are affected.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202605-4061). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.7
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/17/2026 Advisory disclosed05/17/2026 VulDB entry created
05/19/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2026-8772 (🔒)
GCVE (CVE): GCVE-0-2026-8772
GCVE (VulDB): GCVE-100-364397
CNNVD: CNNVD-202605-4061 - litemall 注入漏洞
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/17/2026 11:41Updated: 05/19/2026 17:46
Changes: 05/17/2026 11:41 (57), 05/19/2026 17:46 (6)
Complete: 🔍
Submitter: berna
Cache ID: 216::103
Submit
Accepted
- Submit #811468: linlinjava litemall up to 1.8.0 SQL Injection (by berna)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.