Show filters
7 Total Results
Displaying 1-7 of 7
Sort by:
Attacker Value
Unknown

CVE-2006-6230

Disclosure Date: December 02, 2006 (last updated October 04, 2023)
SQL injection vulnerability in vuBB 0.2.1 and earlier allows remote attackers to execute arbitrary SQL commands via the user parameter in a register action to index.php, a different vulnerability than CVE-2006-0962.
0
0
Attacker Value
Unknown

CVE-2006-6231

Disclosure Date: December 02, 2006 (last updated October 04, 2023)
vuBB 0.2.1 and earlier allows remote attackers to obtain sensitive information via a direct request to includes/vubb.php, which leaks the path in an error message.
0
0
Attacker Value
Unknown

CVE-2006-0962

Disclosure Date: March 02, 2006 (last updated February 22, 2025)
SQL injection vulnerability in vuBB 0.2 allows remote attackers to execute arbitrary SQL commands via the pass parameter in a cookie.
0
0
Attacker Value
Unknown

CVE-2005-4613

Disclosure Date: December 31, 2005 (last updated February 22, 2025)
Cross-site scripting (XSS) vulnerability in VUBB alpha rc1 allows remote attackers to inject arbitrary web script or HTML via unspecified fields in the user edit profile.
0
0
Attacker Value
Unknown

CVE-2005-4612

Disclosure Date: December 31, 2005 (last updated February 22, 2025)
Multiple SQL injection vulnerabilities in VUBB alpha rc1 allow remote attackers to execute arbitrary SQL commands via the (1) f parameter to viewforum.php, (2) t parameter to viewtopic.php, and (3) view parameter to usercp.php.
0
0
Attacker Value
Unknown

CVE-2005-3513

Disclosure Date: November 06, 2005 (last updated February 22, 2025)
index.php in VUBB alpha rc1 allows remote attackers to obtain the installation path of the application via a viewforum action with the f parameter set to a single quote (').
0
0
Attacker Value
Unknown

CVE-2005-3512

Disclosure Date: November 06, 2005 (last updated February 22, 2025)
Cross-site scripting (XSS) vulnerability in index.php in VUBB alpha rc1 allows remote attackers to inject arbitrary web script or HTML via the t parameter in a newreply action.
0
0