Devil-00

**Name of the Vulnerable Software and Affected Versions** Open Bulletin Board (OpenBB) version 1.0.8 **Description** The issue allows remote attackers to obtain the full path of the web server. This can be achieved by providing an invalid `pforums` parameter to API endpoints such as "misc.php" and "member.php". **Recommendations** For OpenBB version 1.0.8, consider restricting access to the "misc.php" and "member.php" endpoints until a patch is available. As a temporary workaround, avoid using the invalid `pforums` parameter in these endpoints to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Invision Gallery version 2.0.6 **Description** The issue allows remote attackers to execute arbitrary SQL commands. This is achieved via the `album` parameter in the "post.php" file. **Recommendations** For Invision Gallery version 2.0.6, update to a newer version that contains a fix for this issue. As a temporary workaround, consider restricting access to the "post.php" file to minimize the risk of exploitation. Avoid using the `album` parameter in the affected endpoint until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** WWWThreads RC 3 **Description** The issue allows remote attackers to execute arbitrary SQL commands. This can be achieved via two methods: 1. the `forumreferrer` cookie to `register.php` 2. the `messages` parameter in `message list.php`. **Recommendations** For WWWThreads RC 3, update the software to prevent SQL injection attacks, specifically by validating and sanitizing user input for the `forumreferrer` cookie and the `messages` parameter. As a temporary workaround, consider restricting access to `register.php` and `message list.php` to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** FlexBB versions 0.5.5 and earlier **Description** The issue allows remote attackers to execute arbitrary SQL commands. This is achieved via the `flexbb username` COOKIE parameter in the "inc/start.php" file. **Recommendations** For FlexBB versions 0.5.5 and earlier, consider restricting access to the `inc/start.php` file until a patch is available. As a temporary workaround, avoid using the `flexbb username` COOKIE parameter in the affected file to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** MyBB versions 1.1 **Description** A cross-site scripting (XSS) issue allows remote attackers to inject arbitrary web script or HTML via the attachment content disposition in an HTML attachment. This could potentially lead to unauthorized actions on the affected system. **Recommendations** For MyBB version 1.1, update to a newer version that contains a fix for this issue to prevent remote attackers from injecting arbitrary web script or HTML.

**Name of the Vulnerable Software and Affected Versions** MyBB versions 1.1.0 **Description** The issue allows remote attackers to initialize arbitrary variables due to the lack of setting the `KILL GLOBAL` constant in global.php and inc/init.php. This could be leveraged to conduct cross-site scripting (XSS) or SQL injection attacks. **Recommendations** For MyBB version 1.1.0, set the `KILL GLOBAL` constant in global.php and inc/init.php to prevent the initialization of arbitrary variables.

Name of the Vulnerable Software and Affected Versions: Arab Portal versions 2.0 Description: The issue concerns multiple cross-site scripting (XSS) vulnerabilities. These vulnerabilities allow remote attackers to inject arbitrary web script or HTML via the `title` parameter in API endpoints such as "online.php" and "download.php". Recommendations: For version 2.0, as a temporary workaround, consider restricting access to the `title` parameter in the affected API endpoints until a patch is available. Avoid using the `title` parameter in "online.php" and "download.php" 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** MyBB versions 1.03 through 1.04 **Description** A SQL injection issue exists, allowing remote attackers to execute arbitrary SQL commands. This occurs when the `register globals` setting is enabled, and the `comma` variable value is set via the `comma` parameter in a cookie. **Recommendations** For MyBB versions 1.03 through 1.04, consider disabling the `register globals` setting to mitigate the risk of SQL injection attacks. As a temporary workaround, restrict access to the `misc.php` file until a patch is available. Avoid using the `comma` parameter in cookies for the affected API endpoint until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** MyBB versions Preview Release 2 **Description** The issue concerns SQL injection vulnerabilities that allow remote attackers to execute arbitrary SQL commands. This can be achieved via the `fid` parameter to "misc.php" or the `Content-Disposition` field in the HTTP header to "newreply.php". **Recommendations** For MyBB version Preview Release 2, update to a newer version that contains a fix for this issue. As a temporary workaround, consider restricting access to the "misc.php" and "newreply.php" scripts to minimize the risk of exploitation. Avoid using the `fid` parameter in the "misc.php" script and the `Content-Disposition` field in the HTTP header to the "newreply.php" script until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Hesk version 0.92 **Description** The issue concerns a problem with username and password verification in the software. Remote attackers can bypass authentication by making a direct request to the "admin main.php" API endpoint. **Recommendations** For Hesk version 0.92, consider disabling access to the "admin main.php" endpoint until a proper fix is available to prevent unauthorized access.

**Name of the Vulnerable Software and Affected Versions** MyBB versions 1.00 Release Candidate 1 through 4 **Description** The issue allows remote attackers to execute arbitrary SQL commands. This is achieved via the `uid` parameter in the "search.php" file. **Recommendations** For MyBB versions 1.00 Release Candidate 1 through 4, avoid using the `uid` parameter in the "search.php" file until the issue is resolved.