PHP Scripts Mall PHP Multivendor Ecommerce seller-view.php usid sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in PHP Scripts Mall PHP Multivendor Ecommerce. This affects an unknown part of the file seller-view.php. This manipulation of the argument usid as part of Parameter causes sql injection. This vulnerability is tracked as CVE-2017-17959. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in PHP Scripts Mall PHP Multivendor Ecommerce (E-Commerce Management Software) (the affected version is unknown). It has been declared as critical. Affected by this vulnerability is an unknown code of the file seller-view.php. The manipulation of the argument usid as part of a Parameter leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
PHP Scripts Mall PHP Multivendor Ecommerce has SQL Injection via the seller-view.php usid parameter.
The bug was discovered 12/28/2017. The weakness was disclosed 12/28/2017 (GitHub Repository). The advisory is shared at github.com. This vulnerability is known as CVE-2017-17959 since 12/28/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:seller-view.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 entries VDB-111149, VDB-111150, VDB-111151 and VDB-111152 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.phpscriptsmall.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.3
VulDB Base Score: 7.3
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: 🔍
Status: Not defined
Google Hack: 🔍
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
12/28/2017 🔍12/28/2017 🔍
12/28/2017 🔍
12/28/2017 🔍
12/29/2017 🔍
03/14/2020 🔍
Sources
Vendor: phpscriptsmall.comAdvisory: github.com
Status: Not defined
CVE: CVE-2017-17959 (🔍)
GCVE (CVE): GCVE-0-2017-17959
GCVE (VulDB): GCVE-100-111157
See also: 🔍
Entry
Created: 12/29/2017 11:44Updated: 03/14/2020 16:06
Changes: 12/29/2017 11:44 (58), 03/14/2020 16:06 (1)
Complete: 🔍
Cache ID: 216:F3E:103
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.