| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in WebAsyst Shop-Script. Affected by this vulnerability is an unknown functionality of the file index.php. Such manipulation of the argument blog_id leads to sql injection. This vulnerability is referenced as CVE-2010-4859. It is possible to launch the attack remotely. Furthermore, an exploit is available.
Details
A vulnerability was found in WebAsyst Shop-Script (affected version unknown). It has been rated as critical. Affected by this issue is an unknown functionality of the file index.php. The manipulation of the argument blog_id 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. CVE summarizes:
SQL injection vulnerability in index.php in WebAsyst Shop-Script allows remote attackers to execute arbitrary SQL commands via the blog_id parameter in a news action.
The weakness was published 10/05/2011 by Vrs-hCk (Website). The advisory is available at securityfocus.com. This vulnerability is handled as CVE-2010-4859 since 10/04/2011. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
The exploit is available at securityfocus.com. It is declared as proof-of-concept. By approaching the search of inurl:index.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 SecurityFocus (BID 40349†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: 🔍
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/03/2009 🔍10/04/2011 🔍
10/05/2011 🔍
10/05/2011 🔍
03/23/2015 🔍
01/29/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Vrs-hCk
Status: Not defined
CVE: CVE-2010-4859 (🔍)
GCVE (CVE): GCVE-0-2010-4859
GCVE (VulDB): GCVE-100-58850
SecurityFocus: 40349 - WebAsyst Shop-Script 'index.php' SQL Injection Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/23/2015 16:50Updated: 01/29/2018 07:54
Changes: 03/23/2015 16:50 (47), 01/29/2018 07:54 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.