Users were able to set an arbitrary "product name" for OX Guard. The chosen value was not sufficiently sanitized before processing it at the user interface, allowing for indirect cross-site scripting attacks. Accounts that were temporarily taken over could be configured to trigger persistent code execution, allowing an attacker to build a foothold. Sanitization is in place for product names now. No publicly available exploits are known.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NOpen Xchange Ox Guard
APPOpen-Xchange2.10.7< 2.10.7
Related vulnerabilities
OX Guard 2.10.4 and earlier allows a Denial of Service via a WKS server that responds slowly or with a large a...
OX Guard 2.8.0 has CSRF.
An issue was discovered in Open-Xchange Guard before 2.2.0-rev8. The "getprivkeybyid" API call is used to down...
An issue was discovered in Open-Xchange OX Guard before 2.4.0-rev8. OX Guard uses an authentication token to i...
OX Guard 2.10.3 and earlier allows XSS.