guanxiCRM Guanxicrm Business Solution up to 0.9.1 appconf[rootpath] file inclusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in guanxiCRM Guanxicrm Business Solution up to 0.9.1 and classified as critical. Affected by this issue is some unknown functionality. Performing a manipulation of the argument appconf[rootpath] results in file inclusion. This vulnerability is known as CVE-2006-4898. Furthermore, an exploit is available.
Details
A vulnerability, which was classified as critical, was found in guanxiCRM Guanxicrm Business Solution up to 0.9.1. This affects an unknown part. The manipulation of the argument appconf[rootpath] with an unknown input leads to a file inclusion vulnerability. CWE is classifying the issue as CWE-73. The product allows user input to control or influence paths or file names that are used in filesystem operations. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
PHP remote file inclusion vulnerability in include/phpxd/phpXD.php in guanxiCRM 0.9.1 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the appconf[rootpath] parameter.
The weakness was published 09/19/2006 by SHiKaA (Website). The advisory is shared at milw0rm.com. This vulnerability is uniquely identified as CVE-2006-4898 since 09/19/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 and a public exploit are known.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
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 (28994), Exploit-DB (2381) and SecurityFocus (BID 20071†). Several companies clearly confirm that VulDB is the primary source for best 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: File inclusionCWE: CWE-73
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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
09/16/2006 🔍09/19/2006 🔍
09/19/2006 🔍
09/19/2006 🔍
03/12/2015 🔍
12/20/2024 🔍
Sources
Advisory: milw0rm.com⛔Researcher: SHiKaA
Status: Not defined
CVE: CVE-2006-4898 (🔍)
GCVE (CVE): GCVE-0-2006-4898
GCVE (VulDB): GCVE-100-32385
X-Force: 28994 - guanxiCRM Business Solution phpxd.php and rfc822.php file include
SecurityFocus: 20071 - GuanxiCRM Business Solution PHPXD.PHP Remote File Include Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/12/2015 15:51Updated: 12/20/2024 05:10
Changes: 03/12/2015 15:51 (53), 09/25/2017 11:29 (1), 07/21/2024 02:11 (24), 12/20/2024 05:10 (2)
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.