LiteCart up to 2.2.1 ?app=users&doc=edit_user cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in LiteCart up to 2.2.1. The affected element is an unknown function of the file admin/?app=users&doc=edit_user. Executing a manipulation can lead to cross-site request forgery. This vulnerability appears as CVE-2020-9018. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability classified as problematic was found in LiteCart up to 2.2.1. This vulnerability affects an unknown functionality of the file admin/?app=users&doc=edit_user. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. CVE summarizes:
LiteCart through 2.2.1 allows admin/?app=users&doc=edit_user CSRF to add a user.
The weakness was presented 02/25/2020. This vulnerability was named CVE-2020-9018 since 02/16/2020. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-150507 for similar entry. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
02/16/2020 🔍02/25/2020 🔍
02/26/2020 🔍
05/11/2025 🔍
Sources
Advisory: cert.ikiu.ac.irStatus: Not defined
CVE: CVE-2020-9018 (🔍)
GCVE (CVE): GCVE-0-2020-9018
GCVE (VulDB): GCVE-100-150508
See also: 🔍
Entry
Created: 02/26/2020 07:54Updated: 05/11/2025 10:06
Changes: 02/26/2020 07:54 (35), 02/26/2020 07:59 (17), 04/02/2024 22:32 (17), 05/11/2025 10:06 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.