This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Daybyday
In DayByDay CRM, versions 1.1 through 2.2.1 (latest) suffer from an application-wide Client-Side Template Injection (CSTI). A low privileged attacker can input template injection payloads in the application at various locations to execute JavaScript on the client browser. (2022-01-13, CVE-2022-22112)
Daybyday 2.1.0 allows stored XSS via the Company Name parameter to the New Client screen. (2020-12-25, CVE-2020-35707)
Daybyday 2.1.0 allows stored XSS via the Name parameter to the New User screen. (2020-12-25, CVE-2020-35705)
Daybyday 2.1.0 allows stored XSS via the Title parameter to the New Lead screen. (2020-12-25, CVE-2020-35704)
Daybyday 2.1.0 allows stored XSS via the Title parameter to the New Project screen. (2020-12-25, CVE-2020-35706)
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>