147 matches found
CVE-2005-3309
Multiple SQL injection vulnerabilities in Zomplog 3.4 allow remote attackers to execute arbitrary SQL commands via 1 the id parameter in detail.php and the catid parameter in 2 get.php and 3 index.php...
CVE-2005-3309: Undefined Security Weakness
Multiple SQL injection vulnerabilities in Zomplog 3.4 allow remote attackers to execute arbitrary SQL commands via 1 the id parameter in detail.php and the catid parameter in 2 get.php and 3 index.php...
CVE-2005-3308: Undefined Security Weakness
Multiple cross-site scripting XSS vulnerabilities in Zomplog 3.4 allow remote attackers to inject arbitrary web script or HTML via the 1 name or 2 comment parameter in detail.php, 3 the username parameter in get.php, and 4 the search parameter in index.php...
Zomplog Script Injection Vulnerability =>3.4 (all versions vulnerable)
zomplog is prone to xss injection attacks. It is possible for a malicious zomplog user to inject hostile xss and script code into the commentary via form fields. This code may be rendered in the browser of a web user who views the commentary of zomplog. zomplog does not adequately filter xss tags...
[SA17306] Zomplog Cross-Site Scripting and SQL Injection Vulnerabilities
TITLE: Zomplog Cross-Site Scripting and SQL Injection Vulnerabilities SECUNIA ADVISORY ID: SA17306 VERIFY ADVISORY: http://secunia.com/advisories/17306/ CRITICAL: Moderately critical IMPACT: Cross Site Scripting, Manipulation of data WHERE: From remote SOFTWARE: Zomplog 3.x...
Zomplog 3.3/3.4 - 'detail.php' HTML Injection
source: https://www.securityfocus.com/bid/15168/info Zomplog is prone to an HTML injection vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input before using it in dynamically generated content. Attacker-supplied HTML and script code would be...
Zomplog 3.33.4 - detail.php HTML Injection
Zomplog 3.33.4 - detail.php HTML Injection source: https://www.securityfocus.com/bid/15168/info Zomplog is prone to an HTML injection vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input before using it in dynamically generated content...