| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in PHPKIT. It has been classified as problematic. This impacts an unknown function of the file imcenter.php. The manipulation of the argument Title leads to cross site scripting. The attack can be initiated remotely. Additionally, an exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in PHPKIT (Content Management System) (unknown version). This issue affects an unknown code block of the file imcenter.php. The manipulation of the argument Titel with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. Impacted is integrity.
The bug was discovered 09/30/2005. The weakness was released 11/07/2005 by Christopher Kunz (Website). The advisory is shared at hardened-php.net. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The exploit is available at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 38 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:imcenter.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 15354†), OSVDB (20558†) and Secunia (SA17479†). Entries connected to this vulnerability are available at VDB-26887, VDB-26886, VDB-26885 and VDB-27664. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.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: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
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: 🔍
Timeline
09/30/2005 🔍11/07/2005 🔍
11/08/2005 🔍
11/08/2005 🔍
11/08/2005 🔍
05/03/2016 🔍
11/06/2018 🔍
Sources
Advisory: hardened-php.netResearcher: Christopher Kunz
Status: Not defined
GCVE (VulDB): GCVE-100-83081
SecurityFocus: 15354 - PHPKit Multiple Input Validation Vulnerabilities
Secunia: 17479 - PHPKIT Multiple Vulnerabilities, Highly Critical
OSVDB: 20558 - PHPKIT imcenter.php Titel Field XSS
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/03/2016 08:35Updated: 11/06/2018 08:04
Changes: 05/03/2016 08:35 (45), 11/06/2018 08:04 (9)
Complete: 🔍
Cache ID: 216:217: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.