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
Fullaspsite Shop Multiple Input-Validation Issues - exploit.company
header-logo
Suggest Exploit
vendor:
Fullaspsite Shop
by:
Unknown
7.5
CVSS
HIGH
Input Validation
79
CWE
Product Name: Fullaspsite Shop
Affected Version From: Unknown
Affected Version To: Unknown
Patch Exists: NO
Related CWE:
CPE:
Metasploit:
Other Scripts:
Platforms Tested: Unknown
Unknown

Fullaspsite Shop Multiple Input-Validation Issues

The Fullaspsite Shop application is prone to multiple input-validation issues, including multiple cross-site scripting issues and an SQL-injection issue. These vulnerabilities occur because the application fails to properly sanitize user-supplied input. An attacker can exploit these vulnerabilities to compromise the application, access or modify data, steal cookie-based authentication credentials, or even exploit vulnerabilities in the underlying database implementation.

Mitigation:

To mitigate these vulnerabilities, it is recommended to implement proper input validation and sanitization techniques. Additionally, keeping the application and underlying software up to date with the latest security patches can help prevent exploitation.
Source

Exploit-DB raw data:

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

Fullaspsite Shop is prone to multiple input-validation issues, including multiple cross-site scripting issues and an SQL-injection issue, because the application fails to properly sanitize user-supplied input.

A successful exploit of these vulnerabilities could allow an attacker to compromise the application, access or modify data, steal cookie-based authentication credentials, or even exploit vulnerabilities in the underlying database implementation. Other attacks are also possible. 

http://www.example.com/ScriptPath/listmain.asp?cat=<script>alert(document.cookie);</script>