Filtered by vendor Xlinesoft
Subscribe
Total
7 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2009-0964 | 1 Xlinesoft | 1 Phprunner | 2024-02-28 | 5.0 MEDIUM | 7.5 HIGH |
UserView_list.php in PHPRunner 4.2, and possibly earlier, stores passwords in cleartext in the database, which allows attackers to gain privileges. NOTE: this can be leveraged with a separate SQL injection vulnerability to obtain passwords remotely without authentication. | |||||
CVE-2009-0963 | 1 Xlinesoft | 1 Phprunner | 2024-02-28 | 7.5 HIGH | N/A |
Multiple SQL injection vulnerabilities in PHPRunner 4.2, and possibly earlier, allow remote attackers to execute arbitrary SQL commands via the SearchField parameter to (1) UserView_list.php, (2) orders_list.php, (3) users_list.php, and (4) Administrator_list.php. | |||||
CVE-2006-5956 | 1 Xlinesoft | 1 Phprunner | 2024-02-28 | 2.1 LOW | N/A |
XLineSoft PHPRunner 3.1 stores the (1) database server name, (2) database names, (3) usernames, and (4) passwords in plaintext in %WINDIR%\PHPRunner.ini, which allows local users to obtain sensitive information by reading the file. | |||||
CVE-2004-2059 | 1 Xlinesoft | 1 Asprunner | 2024-02-28 | 5.0 MEDIUM | N/A |
Multiple cross-site scripting vulnerabilities in ASPRunner 2.4 allow remote attackers to inject arbitrary web script or HTML via the (1) SearchFor parameter in [TABLE-NAME]_search.asp, (2) SQL parameter in [TABLE-NAME]_edit.asp, (3) SearchFor parameter in [TABLE]_list.asp, or (4) SQL parameter in export.asp. | |||||
CVE-2004-2058 | 1 Xlinesoft | 1 Asprunner | 2024-02-28 | 5.0 MEDIUM | N/A |
ASPRunner 2.4 allows remote attackers to gain sensitive information via (1) hidden form fields or (2) error messages. | |||||
CVE-2004-2057 | 1 Xlinesoft | 1 Asprunner | 2024-02-28 | 7.5 HIGH | N/A |
SQL injection vulnerability in ASPRunner 2.4 allows remote attackers to execute arbitrary SQL statements. | |||||
CVE-2004-2060 | 1 Xlinesoft | 1 Asprunner | 2024-02-28 | 5.0 MEDIUM | N/A |
ASPRunner 2.4 stores the database under the web root in the db directory, which may allow remote attackers to obtain the database via a direct request to the database filename, which is predictable based on table and field names. |