This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Ox App Suite
OX App Suite through 8.2 allows XSS via an attachment or OX Drive content when a client uses the len or off parameter. (2022-10-25, CVE-2022-31468)
OX App Suite through 7.10.6 allows XSS via appHandler in a deep link in an e-mail message. (2022-07-27, CVE-2022-23101)
OX App Suite through 7.10.5 allows XSS via a trailing control character such as the SCRIPT\t substring. (2022-03-28, CVE-2021-44212)
OX App Suite through 7.10.5 allows XSS via uuencoding in a multipart/alternative message. (2022-03-28, CVE-2021-44213)
OX App Suite through 7.10.5 allows XSS via an HTML 5 element such as AUDIO. (2022-03-28, CVE-2021-44209)
OX App Suite through 7.10.5 allows XSS via an unknown system message in Chat. (2022-03-28, CVE-2021-44208)
OX App Suite through 7.10.5 allows XSS via NIFF (Notation Interchange File Format) data. (2022-03-28, CVE-2021-44210)
OX App Suite through 7.10.5 allows XSS via the class attribute of an element in an HTML e-mail signature. (2022-03-28, CVE-2021-44211)
OX App Suite 7.10.5 allows XSS via an OX Chat room name. (2021-11-22, CVE-2021-33492)
OX App Suite 7.10.5 allows XSS via an OX Chat room title during typing rendering. (2021-11-22, CVE-2021-33494)
OX App Suite 7.10.5 allows XSS via an OX Chat system message. (2021-11-22, CVE-2021-33495)
OX App Suite through 7.10.5 allows XSS via the alt attribute of an IMG element in a truncated e-mail message. (2021-11-22, CVE-2021-38375)
OX App Suite through through 7.10.5 allows XSS via a crafted snippet that has an app loader reference within an app loader URL. (2021-11-22, CVE-2021-38374)
OX App Suite through 7.10.5 allows XSS via a crafted snippet in a shared mail signature. (2021-11-22, CVE-2021-33490)
OX App Suite through 7.10.5 allows XSS via JavaScript code in a shared XCF file. (2021-11-22, CVE-2021-33489)
Why Cross-site Scripting can be dangerous
Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.
The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:
https://server.com/confirmation?message=Transaction+Complete
what results in:
<span>Confirmation: Transaction Complete</span>
In that case the message can be modified to become a valid Javascript code, e.g.:
https://server.com/confirmation?message=<script>dangerous javascript code here</script>
and it will be executed locally by the user's browser with full access to the user's personal application/browser data:
<span>Confirmation: <script>dangerous javascript code here</script></span>