Fco Javier Puerta Rubio

**Name of the Vulnerable Software and Affected Versions** Cezanne versions 6.5.1 and 7 **Description** A cross-site scripting (XSS) issue allows remote attackers to inject arbitrary web script or HTML via the `SleUserName` parameter in the CFLogon/CFLogon.asp page. This could potentially lead to unauthorized actions on the affected system. **Recommendations** For versions 6.5.1 and 7, consider restricting access to the CFLogon/CFLogon.asp page until a fix is available, and avoid using the `SleUserName` parameter in this context to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Cezanne version 7 **Description** The issue allows remote authenticated users to execute arbitrary SQL commands. This is achieved via the `FUNID` parameter to specific API endpoints: "/CFLookup.asp" and "/CznCommon/CznCustomContainer.asp". **Recommendations** For version 7, consider restricting access to the `FUNID` parameter in the affected API endpoints until a patch is available. As a temporary workaround, avoid using the `FUNID` parameter in the "/CFLookup.asp" and "/CznCommon/CznCustomContainer.asp" endpoints to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Cezanne versions 6.5.1 through 7 **Description** The issue allows remote attackers to inject arbitrary web script or HTML via several parameters to various API endpoints, including '/CFLookUP.asp' with `LookUPId` and `CbFun` parameters, '/CznCommon/CznCustomContainer.asp' with `TitleParms`, `WidgetsHeights`, `WidgetsLinks`, and `WidgetsTitles` parameters, '/home.asp' with `CFTARGET` parameter, '/PeopleWeb/Cards/CVCard.asp' with `PersonOid` parameter, '/PeopleWeb/Cards/PayrollCard.asp' with `DESTLINKOID` and `PersonOID` parameters, and '/PeopleWeb/CznDocFolder/CznDFStartProcess.asp' with `FolderTemplateId` and `FolderTemplateName` parameters. **Recommendations** For Cezanne versions 6.5.1 through 7, consider disabling the affected parameters to mitigate the risk of exploitation until a patch is available. Restrict access to the vulnerable API endpoints to minimize the risk of exploitation. Avoid using the specified parameters in the affected API endpoints until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.