| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Plume CMS 1.0.3. It has been classified as critical. Affected is an unknown function. This manipulation of the argument _PX_config[manager_path] causes code injection. The identification of this vulnerability is CVE-2006-2645. There is no exploit available.
Details
A vulnerability has been found in Plume CMS 1.0.3 (Content Management System) and classified as critical. Affected by this vulnerability is an unknown code block. The manipulation of the argument _PX_config[manager_path] with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
PHP remote file inclusion vulnerability in manager/frontinc/prepend.php for Plume 1.0.3 allows remote attackers to execute arbitrary code via a URL in the _PX_config[manager_path] parameter. NOTE: this is a different executable and affected version than CVE-2006-0725.
The weakness was shared 05/30/2006 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2006-2645 since 05/30/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
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 (27699), Secunia (SA20310†) and SecurityTracker (ID 1016165†). The entry VDB-28751 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
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.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: Code injectionCWE: CWE-94 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/26/2006 🔍05/29/2006 🔍
05/30/2006 🔍
05/30/2006 🔍
05/30/2006 🔍
03/12/2015 🔍
07/27/2018 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2006-2645 (🔍)
GCVE (CVE): GCVE-0-2006-2645
GCVE (VulDB): GCVE-100-30469
X-Force: 27699 - Plume CMS /manager/frontinc/prepend.php file include
Secunia: 20310 - Plume CMS "/manager/frontinc/prepend.php" File Inclusion, Highly Critical
SecurityTracker: 1016165
Vupen: ADV-2006-2014
See also: 🔍
Entry
Created: 03/12/2015 12:19Updated: 07/27/2018 09:16
Changes: 03/12/2015 12:19 (58), 07/27/2018 09:16 (1)
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.