| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Tgs Cms up to 0.1.7. This issue affects some unknown processing of the file logout.php. The manipulation leads to sql injection. This vulnerability is referenced as CVE-2006-5732. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability was found in Tgs Cms up to 0.1.7 (Content Management System) and classified as critical. This issue affects an unknown functionality of the file logout.php. The manipulation 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 integrity. The summary by CVE is:
SQL injection vulnerability in logout.php in T.G.S. CMS 0.1.7 and earlier allows remote attackers to execute arbitrary SQL commands via the myauthorid cookie.
The weakness was published 11/06/2006 by Kacper (Website). The advisory is shared at milw0rm.com. The identification of this vulnerability is CVE-2006-5732 since 11/06/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The exploit is available at securityfocus.com. It is declared as proof-of-concept. By approaching the search of inurl:logout.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 (29941), Exploit-DB (2694) and SecurityFocus (BID 20850†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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
11/01/2006 🔍11/06/2006 🔍
11/06/2006 🔍
11/06/2006 🔍
03/12/2015 🔍
04/26/2026 🔍
Sources
Advisory: milw0rm.com⛔Researcher: Kacper
Status: Not defined
Confirmation: 🔍
CVE: CVE-2006-5732 (🔍)
GCVE (CVE): GCVE-0-2006-5732
GCVE (VulDB): GCVE-100-33125
X-Force: 29941
SecurityFocus: 20850 - T.G.S. CMS Logout.PHP SQL Injection Vulnerability
Vupen: ADV-2006-4667
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/12/2015 22:21Updated: 04/26/2026 10:44
Changes: 03/12/2015 22:21 (49), 09/28/2017 09:23 (8), 08/04/2024 18:39 (19), 12/21/2024 05:34 (4), 04/26/2026 10:44 (2)
Complete: 🔍
Cache ID: 216::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.