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
PHP Bible Search SQL Injection and Cross-Site Scripting Vulnerabilities - exploit.company
header-logo
Suggest Exploit
vendor:
PHP Bible Search
by:
Unknown
7.5
CVSS
HIGH
SQL Injection and Cross-Site Scripting
89 and 79
CWE
Product Name: PHP Bible Search
Affected Version From: All versions prior to the fix
Affected Version To:
Patch Exists: NO
Related CWE:
CPE: a:php_bible_search_project:php_bible_search
Metasploit:
Other Scripts:
Platforms Tested:
2010

PHP Bible Search SQL Injection and Cross-Site Scripting Vulnerabilities

PHP Bible Search is prone to an SQL-injection vulnerability and a cross-site scripting vulnerability because it fails to sufficiently sanitize user-supplied data. Exploiting these issues could allow an attacker to steal cookie-based authentication credentials, compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.

Mitigation:

To mitigate the SQL-injection vulnerability, ensure that input is properly sanitized and validated. To mitigate the cross-site scripting vulnerability, ensure that user-supplied input is properly encoded and sanitized before being displayed to users.
Source

Exploit-DB raw data:

source: https://www.securityfocus.com/bid/41197/info

PHP Bible Search is prone to an SQL-injection vulnerability and a cross-site scripting vulnerability because it fails to sufficiently sanitize user-supplied data.

Exploiting these issues could allow an attacker to steal cookie-based authentication credentials, compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. 

http://www.example.com/bible.php?string=&book=2&chapter=[SQLI]