ProfitCode PayProCart 3.0 adminshop/index.php ftoedit Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ProfitCode PayProCart 3.0. It has been classified as critical. This affects an unknown part of the file adminshop/index.php. The manipulation of the argument ftoedit leads to Remote Code Execution. This vulnerability is referenced as CVE-2005-1005. Furthermore, an exploit is available.
Details
A vulnerability was found in ProfitCode PayProCart 3.0. It has been rated as critical. This issue affects an unknown code block of the file adminshop/index.php. The manipulation of the argument ftoedit with an unknown input leads to a remote code execution vulnerability. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
ProfitCode PayProCart 3.0 allows remote attackers to bypass authentication and gain administrative privileges to the admin control panel, as demonstrated via a direct request to adminshop/index.php with hex-encoded .. sequences in the ftoedit parameter.
The weakness was published 05/02/2005 (Website). The advisory is shared at marc.theaimsgroup.com. The identification of this vulnerability is CVE-2005-1005 since 04/07/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.
The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:adminshop/index.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 X-Force (19956), Exploit-DB (25338), SecurityFocus (BID 13006†), Secunia (SA14832†) and SecurityTracker (ID 1013640†). Similar entries are available at VDB-24784 and VDB-24783. 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: Remote Code ExecutionCWE: Unknown
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-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
04/04/2005 🔍04/05/2005 🔍
04/07/2005 🔍
05/02/2005 🔍
05/02/2005 🔍
03/10/2015 🔍
10/30/2025 🔍
Sources
Advisory: marc.theaimsgroup.comStatus: Not defined
CVE: CVE-2005-1005 (🔍)
GCVE (CVE): GCVE-0-2005-1005
GCVE (VulDB): GCVE-100-24785
X-Force: 19956 - PayProCart index.php bypass authentication
SecurityFocus: 13006
Secunia: 14832 - PayProCart Multiple Vulnerabilities, Moderately Critical
SecurityTracker: 1013640
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/10/2015 23:05Updated: 10/30/2025 17:26
Changes: 03/10/2015 23:05 (50), 07/07/2018 10:19 (7), 10/30/2025 17:26 (27)
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.