Courier Management System 1.0 admin_class.php ref_no sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Courier Management System 1.0. This affects an unknown part of the file admin_class.php. The manipulation of the argument ref_no results in sql injection. This vulnerability is known as CVE-2020-35327. It is possible to launch the attack remotely. Furthermore, an exploit is available.
Details
A vulnerability was found in Courier Management System 1.0. It has been classified as critical. Affected is an unknown code block of the file admin_class.php. The manipulation of the argument ref_no with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 03/05/2021 as 49243. The advisory is shared for download at exploit-db.com. This vulnerability is traded as CVE-2020-35327. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:admin_class.php it is possible to find vulnerable targets with Google Hacking.
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 Exploit-DB (49243). 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: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: 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: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/14/2020 🔍03/05/2021 🔍
03/05/2021 🔍
03/28/2021 🔍
Sources
Advisory: 49243Status: Not defined
CVE: CVE-2020-35327 (🔍)
GCVE (CVE): GCVE-0-2020-35327
GCVE (VulDB): GCVE-100-170700
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/05/2021 07:36Updated: 03/28/2021 12:21
Changes: 03/05/2021 07:36 (41), 03/07/2021 09:23 (2), 03/28/2021 12:21 (18)
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.