| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in PKR Internet Taskjitsu up to 2.0.5. The affected element is an unknown function. Performing a manipulation of the argument Query results in sql injection. This vulnerability was named CVE-2006-5184. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in PKR Internet Taskjitsu up to 2.0.5. This affects some unknown functionality. The manipulation of the argument query with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in PKR Internet Taskjitsu before 2.0.6 allows remote attackers to execute arbitrary SQL commands via the key parameter, when the limit query parameter is set to customerid.
The weakness was presented 10/10/2006 (Website). It is possible to read the advisory at pkrinternet.com. This vulnerability is uniquely identified as CVE-2006-5184 since 10/06/2006. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
It is declared as proof-of-concept.
Upgrading to version 2.0.6 eliminates this vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 20332†), Secunia (SA22257†) and SecurityTracker (ID 1016978†). Statistical analysis made it clear that VulDB provides the best quality 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: 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: 🔍
Status: Proof-of-Concept
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Taskjitsu 2.0.6
Timeline
10/04/2006 🔍10/04/2006 🔍
10/04/2006 🔍
10/06/2006 🔍
10/10/2006 🔍
10/10/2006 🔍
03/12/2015 🔍
04/23/2026 🔍
Sources
Advisory: pkrinternet.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2006-5184 (🔍)
GCVE (CVE): GCVE-0-2006-5184
GCVE (VulDB): GCVE-100-32643
SecurityFocus: 20332 - Taskjitsu Key Parameter SQL Injection Vulnerability
Secunia: 22257 - Taskjitsu "key" SQL Injection Vulnerability, Moderately Critical
SecurityTracker: 1016978
Vupen: ADV-2006-3903
Entry
Created: 03/12/2015 15:51Updated: 04/23/2026 21:02
Changes: 03/12/2015 15:51 (56), 08/05/2018 06:43 (6), 04/23/2026 21:02 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.