8 matches found
EUVD-2007-4079
Malware in sbrugna...
BSM Store Dependent Forums 1.02 UserName Parameter SQL Injection Vulnerability
No description provided by source. source: http://www.securityfocus.com/bid/25072/info BSM Store Dependent Forums is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data before using it in an SQL query. Exploiting this issue could allow an attacker ...
Sql injection
SQL injection vulnerability in BSM Store Dependent Forums 1.02 allows remote attackers to execute arbitrary SQL commands via a Username field in an unspecified component, probably the FrmUserName parameter in login.asp...
CVE-2007-4095
SQL injection vulnerability in BSM Store Dependent Forums 1.02 allows remote attackers to execute arbitrary SQL commands via a Username field in an unspecified component, probably the FrmUserName parameter in login.asp...
CVE-2007-4095
CVE-2007-4095 describes an SQL injection in BSM Store Dependent Forums 1.02, likely via the FrmUserName parameter in login.asp (Username field). The vulnerability allows remote attackers to execute arbitrary SQL commands, impacting data confidentiality, integrity, and potentially availability as ...
CVE-2007-4095
SQL injection vulnerability in BSM Store Dependent Forums 1.02 allows remote attackers to execute arbitrary SQL commands via a Username field in an unspecified component, probably the FrmUserName parameter in login.asp...
CVE-2007-4095: Improper Neutralization of Special Elements used in an SQL Command
SQL injection vulnerability in BSM Store Dependent Forums 1.02 allows remote attackers to execute arbitrary SQL commands via a Username field in an unspecified component, probably the FrmUserName parameter in login.asp...
BSM Store Dependent Forums 1.02 - Username SQL Injection
BSM Store Dependent Forums 1.02 - Username SQL Injection source: https://www.securityfocus.com/bid/25072/info BSM Store Dependent Forums is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data before using it in an SQL query. Exploiting this issue...