Vulnerabilities

A vulnerability classified as critical has been found in playSMS 1.4.4/1.4.5/1.4.6/1.4.7.

A vulnerability was found in playSMS 1.4.3.

A vulnerability was found in playSMS 1.4.3.

A vulnerability, which was classified as problematic, was found in playSMS 1.4.3.

A type juggling vulnerability in the component /auth/fn.php of PlaySMS v1.4.5 and earlier allows attackers to bypass authentication.

playSMS before 1.4.5 allows Arbitrary Code Execution by entering PHP code at the #tabs-information-page of core_main_config, and then executing that code via the index.php?app=main&inc=core_welcome URI.

playSMS through 1.4.3 is vulnerable to session fixation.

PlaySMS before 1.4.3 does not sanitize inputs from a malicious string.

import.php (aka the Phonebook import feature) in PlaySMS 1.4 allows remote code execution via vectors involving the User-Agent HTTP header and PHP code in the name of a file.

PlaySMS 1.4 allows remote code execution because PHP code in the name of an uploaded .php file is executed.

Multiple PHP remote file inclusion vulnerabilities in playSMS 0.9.3 allow remote attackers to execute arbitrary PHP code via a URL in the (1) apps_path[plug] parameter to plugin/gateway/gnokii/init.php, the (2) apps_path…

Multiple directory traversal vulnerabilities in playSMS 0.9.3 allow remote attackers to include and execute arbitrary local files via directory traversal sequences in the (1) gateway_module parameter to plugin/gateway/gn…

Cross-site scripting (XSS) vulnerability in index.php in PlaySMS 0.8 allows remote attackers to inject arbitrary web script or HTML via the err parameter.

SQL injection vulnerability in the valid function in fr_left.php in PlaySMS 0.7 and earlier allows remote attackers to modify SQL statements via the vc2 cookie.