Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-pagenavi domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/u918112125/domains/exploit.company/public_html/wp-includes/functions.php on line 6114
phpBugTracker Multiple Input Validation Vulnerabilities - exploit.company
header-logo
Suggest Exploit
vendor:
phpBugTracker
by:
Unknown
7.5
CVSS
HIGH
SQL Injection, Cross-site Scripting, HTML Injection
Unknown
CWE
Product Name: phpBugTracker
Affected Version From: Unknown
Affected Version To: Unknown
Patch Exists: NO
Related CWE: Unknown
CPE: Unknown
Metasploit:
Other Scripts:
Platforms Tested:
Unknown

phpBugTracker Multiple Input Validation Vulnerabilities

Multiple input validation vulnerabilities in phpBugTracker allow remote attackers to execute arbitrary SQL commands via the (1) bugid parameter in bug.php, or execute arbitrary script code via the (2) op parameter in bug.php or (3) op parameter in user.php.

Mitigation:

Unknown
Source

Exploit-DB raw data:

source: https://www.securityfocus.com/bid/10153/info
 
Reportedly phpBugTracker contains multiple input validation vulnerabilities; it is prone to multiple SQL injection, cross-site scripting and HTML injection issues. These issues are all due to a failure of the application to properly sanitize user supplied input.
 
The SQL injection issues may allow a remote attacker to manipulate query logic, potentially leading to unauthorized access to sensitive information such as the administrator password hash or corruption of database data. SQL injection attacks may also potentially be used to exploit latent vulnerabilities in the underlying database implementation.
 
The cross-site scripting and HTML injection issues may allow an attacker to execute arbitrary script code in the browser of an unsuspecting user. It may be possible to steal the unsuspecting user's cookie-based authentication credentials, as well as other sensitive information. Other attacks may also be possible.

http://www.example.com/bug.php?op=vote&bugid=[SQL]
http://www.example.com/bug.php?op=viewvotes&bugid=[SQL]
http://www.example.com/user.php?op=delvote&bugid=[SQL]