EUVD-2005-3937

Malware in sbrugna...

Orca Knowledgebase 2.1 Knowledgebase.PHP SQL Injection Vulnerability

No description provided by source. source: http://www.securityfocus.com/bid/15637/info Orca Knowledgebase is prone to an SQL injection vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input before using it in an SQL query. Successful exploitation...

CVE-2005-3942

SQL injection vulnerability in knowledgebase-control.php in Orca Knowledgebase 2.1b and earlier allows remote attackers to execute arbitrary SQL commands via the qid parameter...

CVE-2005-3942

CVE-2005-3942 pertains to Orca Knowledgebase, affected in version 2.1b and earlier. The vulnerability is a SQL injection in the knowledgebase-control.php component, exploited via the qid parameter, allowing remote attackers to execute arbitrary SQL commands. The available documents do not provide...

CVE-2005-3942

SQL injection vulnerability in knowledgebase-control.php in Orca Knowledgebase 2.1b and earlier allows remote attackers to execute arbitrary SQL commands via the qid parameter...

Orca KnowledgeBase 2.1 - 'KnowledgeBase.php' SQL Injection

source: https://www.securityfocus.com/bid/15637/info Orca Knowledgebase is prone to an SQL injection vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input before using it in an SQL query. Successful exploitation could result in a compromise of t...

Orca Knowledgebase SQL vuln.

Orca Knowledgebase SQL vuln. Vuln. dicovered by : r0t Date: 29 nov. 2005 orginal advisory:http://pridels.blogspot.com/2005/11/orca-knowledgebase-sql-vuln.html Vendor:http://www.greywyvern.com/orcaknow affected version: 2.1b and prior Product Description: The Orca Knowledgebase is the simplest way...

Orca KnowledgeBase 2.1 - KnowledgeBase.php SQL Injection

Orca KnowledgeBase 2.1 - KnowledgeBase.php SQL Injection source: https://www.securityfocus.com/bid/15637/info Orca Knowledgebase is prone to an SQL injection vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input before using it in an SQL query...