Omni

**Name of the Vulnerable Software and Affected Versions** eForum version 0.4 **Description** The issue concerns multiple cross-site scripting (XSS) vulnerabilities. These vulnerabilities allow remote attackers to inject arbitrary web script or HTML via the `busca` and `link` parameters in the busca.php file. **Recommendations** For eForum version 0.4, consider validating and sanitizing user input for the `busca` and `link` parameters to prevent XSS attacks. As a temporary workaround, restrict access to the busca.php file until a patch is available.

**Name of the Vulnerable Software and Affected Versions** LightBlog version 9.5 **Description** The issue allows remote attackers to execute arbitrary code by uploading a file with an executable extension to the blog's root directory via the cp upload image.php script, and then accessing it directly. **Recommendations** For LightBlog version 9.5, consider restricting or disabling the cp upload image.php script until a patch is available to prevent remote attackers from uploading executable files. Additionally, restrict access to the blog's root directory to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** FTP Admin version 0.1.0 **Description** A cross-site scripting (XSS) issue exists, allowing remote attackers to inject arbitrary web script or HTML via the `error` parameter in an error page action. This occurs in the index.php file. **Recommendations** For FTP Admin version 0.1.0, update the index.php file to properly sanitize the `error` parameter to prevent XSS attacks. As a temporary workaround, consider restricting access to the error page action until a patch is available.

**Name of the Vulnerable Software and Affected Versions** FTP Admin version 0.1.0 **Description** A directory traversal issue exists, allowing remote authenticated users to include and execute arbitrary local files by using a .. (dot dot) in the `page` parameter of the index.php file. In certain environments, this can be exploited for remote file inclusion using a UNC share pathname or an ftp, ftps, or ssh2.sftp URL. **Recommendations** For FTP Admin version 0.1.0, consider restricting access to the index.php file until a patch is available, and avoid using the `page` parameter with untrusted input to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** FTP Admin version 0.1.0 **Description** The issue allows remote attackers to bypass authentication and obtain administrative access. This can be achieved by manipulating the `loggedin` parameter with a value of `true`. An example of exploitation includes adding a user account. **Recommendations** For FTP Admin version 0.1.0, consider restricting access to the `index.php` file until a patch is available. As a temporary workaround, avoid using the `loggedin` parameter with a value of `true` in the affected API endpoint.

**Name of the Vulnerable Software and Affected Versions** QDBlog versions 0.4 and earlier **Description** The issue concerns directory traversal vulnerabilities. Remote attackers can include and execute arbitrary local files by using a .. (dot dot) in the `theme` parameter to "categories.php" and other unspecified files. **Recommendations** For QDBlog versions 0.4 and earlier, consider restricting access to the `categories.php` file and other unspecified files that are vulnerable to directory traversal attacks until a patch is available. As a temporary workaround, avoid using the `theme` parameter in the affected API endpoint until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** QDBlog versions 0.4 and earlier **Description** The issue concerns SQL injection vulnerabilities in the authenticate.php file. Remote attackers can execute arbitrary SQL commands by manipulating the `username` and `password` parameters. **Recommendations** For QDBlog versions 0.4 and earlier, update to a version that fixes the SQL injection vulnerabilities in the authenticate.php file. As a temporary workaround, consider restricting access to the authenticate.php file to minimize the risk of exploitation. Avoid using the `username` and `password` parameters in a way that could allow SQL injection until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** pL-PHP beta version 0.9 **Description** The issue allows remote attackers to execute arbitrary SQL commands. This is achieved via the `login` or `pass` parameter in the login.php file. **Recommendations** For pL-PHP beta version 0.9, consider validating and sanitizing user input for the `login` and `pass` parameters to prevent SQL injection attacks. As a temporary workaround, restrict access to the login.php file until a patch is available.

**Name of the Vulnerable Software and Affected Versions** pL-PHP beta version 0.9 **Description** A directory traversal issue exists, allowing remote attackers to include and execute arbitrary local files. This is achieved by using a .. (dot dot) in the `lang` parameter of the admin.php file. **Recommendations** For pL-PHP beta version 0.9, consider restricting access to the admin.php file until a patch is available, and avoid using the `lang` parameter with untrusted input.

**Name of the Vulnerable Software and Affected Versions** pL-PHP beta version 0.9 **Description** The issue allows remote attackers to bypass authentication. This is achieved by setting the `is admin` parameter to 1 in the admin.php file. **Recommendations** For pL-PHP beta version 0.9, restrict access to the admin.php file to prevent unauthorized access until a fix is available. As a temporary workaround, consider validating and sanitizing the `is admin` parameter to prevent its manipulation.