CVE-2005-0670 in phpCOIN
Summary
by MITRE
Cross-site scripting (XSS) vulnerability in phpCOIN 1.2.0 through 1.2.1b allows remote attackers to inject arbitrary web script or HTML via (1) the new parameter to mod.php, (2) the w parameter to mod.php, (3) the e parameter to login.php, (4) the o parameter to login.php, and possibly other scripts.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 09/29/2025
The vulnerability described in CVE-2005-0670 represents a critical cross-site scripting flaw affecting phpCOIN versions 1.2.0 through 1.2.1b. This weakness enables remote attackers to execute malicious scripts within the context of other users' browsers, fundamentally compromising the security of web applications that rely on this content management system. The vulnerability manifests through multiple attack vectors, specifically targeting parameter handling in key application scripts including mod.php and login.php, demonstrating a widespread failure in input validation and output sanitization practices.
The technical implementation of this vulnerability stems from insufficient validation of user-supplied input parameters within the affected phpCOIN scripts. Attackers can exploit the new parameter in mod.php, the w parameter in the same file, the e parameter in login.php, and the o parameter in login.php to inject malicious payloads that will be executed when other users view the affected pages. These parameters likely receive direct user input without proper sanitization or encoding, creating an environment where arbitrary HTML and JavaScript code can be injected into web responses. This type of vulnerability falls under CWE-79 which specifically addresses Cross-Site Scripting flaws in software applications.
The operational impact of this vulnerability extends beyond simple data theft or defacement. An attacker could leverage this weakness to steal session cookies, redirect users to malicious sites, perform actions on behalf of authenticated users, or even establish persistent backdoors within the web application. The broad scope of affected parameters across multiple scripts increases the attack surface significantly, making it easier for threat actors to find a successful exploitation path. This vulnerability particularly impacts web applications that depend on phpCOIN for content management, potentially affecting numerous websites and organizations that have not updated to patched versions.
Organizations affected by this vulnerability should immediately implement mitigation strategies including input validation and output encoding for all user-supplied parameters, applying the latest security patches from phpCOIN developers, and implementing web application firewalls to detect and block malicious script injection attempts. The remediation process should involve thorough code review of all parameter handling within the application, particularly focusing on the identified vulnerable scripts. Security monitoring should be enhanced to detect unusual parameter patterns, and regular security assessments should be conducted to identify similar vulnerabilities in other web applications. Additionally, implementing proper content security policies and using secure coding practices aligned with OWASP Top Ten recommendations would significantly reduce the risk of exploitation in similar scenarios.