Profitcode maintains e-commerce payment-processing solutions centered around its PayProCart and PPalCart product line, which handle transaction flows and cart management for online retailers. The recurring vulnerability signal centers on code-injection risks within these payment-processing components, reflecting the input-handling demands of systems that process user-supplied transaction data. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Profitcode over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2006-4672HIGH PHP remote file inclusion vulnerability in profitCode ppalCart 2.5 EE, possibly a component of PayProCart, allows remote attackers to execute arbitrary PHP code via a URL in the (1 | Sep 11, 2006 | 7.5 | 29 | NO | YES |
CVE-2005-1005HIGH 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 ad | May 2, 2005 | 7.5 | 29 | NO | YES |
CVE-2005-1004MEDIUM Cross-site scripting (XSS) vulnerability in usrdetails.php in ProfitCode PayProCart 3.0 allows remote attackers to inject arbitrary web script or HTML via the sgnuptype parameter. | May 2, 2005 | 4.3 | 22 | NO | YES |
CVE-2005-1003HIGH Directory traversal vulnerability in index.php for ProfitCode PayProCart 3.0 allows remote attackers to include arbitrary PHP files via .. (dot dot) sequences in the modID paramete | May 2, 2005 | 7.5 | 20 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Profitcode.
Media articles that mention a CVE ID that affects a product developed by Profitcode — matched by CVE ID, not by vendor name.