| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.45 |
Summary
A vulnerability was found in intouch 0.5.1 Alpha. It has been classified as critical. This affects an unknown function in the library intouch.lib.php. This manipulation of the argument User causes sql injection. This vulnerability is handled as CVE-2006-0088. The attack can be initiated remotely. Additionally, an exploit exists.
Details
A vulnerability has been found in intouch 0.5.1 Alpha and classified as critical. Affected by this vulnerability is an unknown code block in the library intouch.lib.php. The manipulation of the argument user with an unknown input 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:
SQL injection vulnerability in intouch.lib.php in inTouch 0.5.1 Alpha allows remote attackers to execute arbitrary SQL commands via the user parameter.
The weakness was released 01/01/2006 by Aliaksandr Hartsuyeu (Website). The advisory is shared at vupen.com. This vulnerability is known as CVE-2006-0088 since 01/05/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:intouch.lib.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 X-Force (23954), Exploit-DB (27003), SecurityFocus (BID 16110†) and OSVDB (22382†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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 |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/01/2006 🔍01/01/2006 🔍
01/05/2006 🔍
01/05/2006 🔍
01/13/2006 🔍
03/12/2015 🔍
12/05/2025 🔍
Sources
Advisory: vupen.com⛔Researcher: Aliaksandr Hartsuyeu
Status: Not defined
CVE: CVE-2006-0088 (🔍)
GCVE (CVE): GCVE-0-2006-0088
GCVE (VulDB): GCVE-100-28201
X-Force: 23954
SecurityFocus: 16110 - InTouch User Variable SQL Injection Vulnerability
OSVDB: 22382 - inTouch intouch.lib.php user Parameter SQL Injection
Vupen: ADV-2006-0026
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/12/2015 11:11Updated: 12/05/2025 00:11
Changes: 03/12/2015 11:11 (50), 08/21/2017 10:22 (6), 12/05/2025 00:11 (24)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.