Scriptphp Messageriescripthp 2.0 lire-avis.php aa sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Scriptphp Messageriescripthp 2.0. This impacts an unknown function of the file lire-avis.php. Such manipulation of the argument aa leads to sql injection. This vulnerability is uniquely identified as CVE-2006-6521. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in Scriptphp Messageriescripthp 2.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file lire-avis.php. The manipulation of the argument aa 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 lire-avis.php in Messageriescripthp 2.0 allows remote attackers to execute arbitrary SQL commands via the aa parameter.
The weakness was disclosed 12/13/2006 (Website). The advisory is shared for download at securityfocus.com. This vulnerability is handled as CVE-2006-6521 since 12/13/2006. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
By approaching the search of inurl:lire-avis.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 databases at SecurityFocus (BID 21513†) and Secunia (SA23319†). The entry VDB-33811 is pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: 🔍
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: 🔍
Suricata ID: 2006345
Suricata Class: 🔍
Suricata Message: 🔍
Timeline
12/09/2006 🔍12/10/2006 🔍
12/13/2006 🔍
12/13/2006 🔍
12/13/2006 🔍
03/12/2015 🔍
08/10/2018 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2006-6521 (🔍)
GCVE (CVE): GCVE-0-2006-6521
GCVE (VulDB): GCVE-100-33812
SecurityFocus: 21513 - Messageriescripthp Multiple Input Validation Vulnerabilities
Secunia: 23319 - Messageriescripthp SQL Injection and Cross-Site Scripting, Moderately Critical
See also: 🔍
Entry
Created: 03/12/2015 22:21Updated: 08/10/2018 06:42
Changes: 03/12/2015 22:21 (52), 08/10/2018 06:42 (7)
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.