Neeraj Kumar

**Name of the Vulnerable Software and Affected Versions** BPC SmartVista version 2 **Description** The issue concerns a session fixation problem via the `JSESSIONID` parameter. **Recommendations** For version 2, consider restricting access to the `JSESSIONID` parameter to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Polaris FT Intellect Core Banking version 9.7.1 **Description** An issue exists in the Core and Portal modules, where an open redirect is possible via the "/IntellectMain.jsp?IntellectSystem=" URI. **Recommendations** For Polaris FT Intellect Core Banking version 9.7.1, consider restricting access to the "/IntellectMain.jsp" endpoint to minimize the risk of exploitation. 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** BPC SmartVista 2 **Description** The issue is related to a CSRF problem. It affects the `/SVFE2/pages/admpages/roles/createrole.jsf` API endpoint. **Recommendations** For BPC SmartVista 2, consider implementing proper CSRF protection mechanisms to prevent exploitation. As a temporary workaround, restrict access to the `/SVFE2/pages/admpages/roles/createrole.jsf` endpoint until a patch is available.

**Name of the Vulnerable Software and Affected Versions** BPC SmartVista 2 **Description** The issue is related to improper access control in the SVFE module. A normal user can access the "SVFE2/pages/finadmin/currconvrate/currconvrate.jsf" functionality, which should only be accessible to an admin. **Recommendations** For BPC SmartVista 2, restrict access to the SVFE2/pages/finadmin/currconvrate/currconvrate.jsf functionality to only admin users as a temporary workaround until a proper fix is available.

**Name of the Vulnerable Software and Affected Versions** Polaris FT Intellect Core Banking version 9.7.1 **Description** An issue in the Armor module allows SQL injection with an authenticated session. This occurs because input passed through the `code` parameter in certain pages, such as "collaterals/colexe3t.jsp", "/references/refsuppu.jsp", and "/references/refbranu.jsp", is mishandled before being used in SQL queries. **Recommendations** For Polaris FT Intellect Core Banking version 9.7.1, consider restricting access to the affected pages, specifically "collaterals/colexe3t.jsp", "/references/refsuppu.jsp", and "/references/refbranu.jsp", to minimize the risk of exploitation. Avoid using the `code` parameter in these pages 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** Polaris FT Intellect Core Banking version 9.7.1 **Description** A reflected XSS issue exists in the Core and Portal modules, which can be exploited with an authenticated session. The issue is related to the `Customerid`, `formName`, `FrameId`, or `MODE` parameters. **Recommendations** For Polaris FT Intellect Core Banking version 9.7.1, consider restricting access to the affected parameters `Customerid`, `formName`, `FrameId`, and `MODE` to minimize the risk of exploitation until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Polaris FT Intellect Core Banking version 9.7.1 **Description** An issue was discovered in the Armor module, allowing CSRF to occur via the "/CollatWebApp/gcmsRefInsert?name=SUPP" URI. **Recommendations** For Polaris FT Intellect Core Banking version 9.7.1, consider implementing CSRF protection mechanisms to prevent exploitation. As a temporary workaround, restrict access to the "/CollatWebApp/gcmsRefInsert?name=SUPP" URI to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Bookme Control Panel version 2.0 **Description** The issue concerns a stored XSS vulnerability within the `Customers` function, specifically in the `Name` and `Note` sections, referred to as `custName` and `custNote`. The application fails to sanitize user-supplied input, allowing injected JavaScript code to be rendered in the user's browser. **Recommendations** For Bookme Control Panel version 2.0, consider implementing input sanitization for the `custName` and `custNote` fields to prevent XSS attacks. As a temporary workaround, restrict the use of the `Customers` function until a proper fix is applied.

**Name of the Vulnerable Software and Affected Versions** PHP Scripts Mall Hot Scripts Clone:Script Classified Version 3.1 **Description** The application is vulnerable to stored XSS within the "Add New" function for a Management User. The issue arises because the application does not sanitize user-supplied input to the `name` parameter, allowing injected JavaScript code to be rendered to the user's browser. **Recommendations** For PHP Scripts Mall Hot Scripts Clone:Script Classified Version 3.1, ensure proper sanitization of user input to the `name` parameter within the "Add New" function to prevent XSS attacks. As a temporary workaround, consider restricting access to the "Add New" function for Management Users until a proper fix is implemented.

**Name of the Vulnerable Software and Affected Versions** PHP Scripts Mall Entrepreneur Job Portal Script version 2.0.9 **Description** The issue concerns a Cross-Site Scripting (XSS) flaw. It is located in the `p name` field, also known as the Edit Category Name field, which is accessible through the "admin/categories industry.php" page, also referred to as Categories - Industry Type. **Recommendations** For PHP Scripts Mall Entrepreneur Job Portal Script version 2.0.9, consider restricting access to the `p name` field in the admin/categories industry.php page until a fix is available. As a temporary workaround, avoid using the `p name` field for editing category names to minimize the risk of exploitation.