PHPKit 1.6.1 Login login/member.php im_receiver sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.6$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in PHPKit 1.6.1. This vulnerability affects unknown code of the file login/member.php of the component Login. Performing a manipulation of the argument im_receiver results in sql injection. This vulnerability is cataloged as CVE-2005-2683. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in PHPKit 1.6.1 (Content Management System). This affects an unknown functionality of the file login/member.php of the component Login. The manipulation of the argument im_receiver 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:

Multiple SQL injection vulnerabilities in PHPKit 1.6.1 allow remote attackers to execute arbitrary SQL commands via the (1) letter parameter to login/member.php or (2) im_receiver parameter to login/imcenter.php.

The bug was discovered 08/22/2005. The weakness was shared 08/23/2005 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2005-2683 since 08/23/2005. 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 and a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:login/member.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 15784 (PHP-Kit <= 1.6.1 RC2 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r.

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 (21963), Exploit-DB (26184), Tenable (15784), SecurityFocus (BID 14629†) and OSVDB (18951†). The entries VDB-26887, VDB-26886, VDB-26885 and VDB-26161 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 15784
Nessus Name: PHP-Kit <= 1.6.1 RC2 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/22/2004 🔍
08/22/2005 +273 days 🔍
08/22/2005 +0 days 🔍
08/22/2005 +0 days 🔍
08/23/2005 +1 days 🔍
08/23/2005 +0 days 🔍
08/23/2005 +0 days 🔍
05/23/2006 +273 days 🔍
03/11/2015 +3214 days 🔍
10/10/2025 +3866 days 🔍

Sourcesinfo

Advisory: securityfocus.com⛔
Status: Not defined

CVE: CVE-2005-2683 (🔍)
GCVE (CVE): GCVE-0-2005-2683
GCVE (VulDB): GCVE-100-26139
X-Force: 21963
SecurityFocus: 14629 - PHPKit Multiple SQL Injection Vulnerabilities
Secunia: 16531
OSVDB: 18951 - PHPKIT imcenter.php and member.php scripts SQL injection
Vulnerability Center: 11554 - PHPKit SQL Injections via member.php \x26 imcenter.php, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/11/2015 23:39
Updated: 10/10/2025 15:39
Changes: 03/11/2015 23:39 (67), 06/18/2019 16:28 (4), 10/10/2025 15:39 (27)
Complete: 🔍
Cache ID: 216:EEF:103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!