Aggregates CVE and security vulnerability intelligence across all daybydaycrm-related products, including CVSS, EPSS, publication dates, and vulnerability intelligence data.
Disclosed issues often relate to vendor risk cross-site scripting; exposure may include vendor impact session compromise in vendor surface software deployment and vendor surface production workloads contexts.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2022-22113 | In DayByDay CRM, versions 2.2.0 through 2.2.1 (latest) are vulnerable to Insufficient Session Expiration. When a password has been changed by the user or by an administrator, a user that was already logged in, will still have access to the application even after the password was changed. | [email protected] | 8.8 | 1.02% | 2022-01-13 | 2026-06-17 |
| CVE-2022-22112 | 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. | [email protected] | 5.4 | 0.62% | 2022-01-13 | 2026-06-17 |
| CVE-2022-22111 | In DayByDay CRM, version 2.2.0 is vulnerable to missing authorization. Any application user in the application who has update user permission enabled is able to change the password of other users, including the administrator’s. This allows the attacker to gain access to the highest privileged user in the application. | [email protected] | 8.8 | 1.00% | 2022-01-05 | 2026-06-17 |
| CVE-2022-22110 | In Daybyday CRM, versions 1.1 through 2.2.0 enforce weak password requirements in the user update functionality. A user with privileges to update his password could change it to a weak password, such as those with a length of a single character. This may allow an attacker to brute-force users’ passwords with minimal to no computational effort. | [email protected] | 7.5 | 1.12% | 2022-01-05 | 2026-06-17 |
| CVE-2022-22109 | In Daybyday CRM, version 2.2.0 is vulnerable to Stored Cross-Site Scripting (XSS) vulnerability that allows low privileged application users to store malicious scripts in the title field of new tasks. These scripts are executed in a victim’s browser when they open the “/tasks” page to view all the tasks. | [email protected] | 5.4 | 0.53% | 2022-01-05 | 2026-06-17 |
| CVE-2022-22108 | In Daybyday CRM, versions 2.0.0 through 2.2.0 are vulnerable to Missing Authorization. An attacker that has the lowest privileges account (employee type user), can view the absences of all users in the system including administrators. This type of user is not authorized to view this kind of information. | [email protected] | 4.3 | 0.68% | 2022-01-05 | 2026-06-17 |
| CVE-2022-22107 | In Daybyday CRM, versions 2.0.0 through 2.2.0 are vulnerable to Missing Authorization. An attacker that has the lowest privileges account (employee type user), can view the appointments of all users in the system including administrators. However, this type of user is not authorized to view the calendar at all. | [email protected] | 4.3 | 0.68% | 2022-01-05 | 2026-06-17 |
| CVE-2020-35707 | Daybyday 2.1.0 allows stored XSS via the Company Name parameter to the New Client screen. | [email protected] | 5.4 | 0.60% | 2020-12-25 | 2026-06-16 |
| CVE-2020-35706 | Daybyday 2.1.0 allows stored XSS via the Title parameter to the New Project screen. | [email protected] | 5.4 | 0.60% | 2020-12-25 | 2026-06-16 |
| CVE-2020-35705 | Daybyday 2.1.0 allows stored XSS via the Name parameter to the New User screen. | [email protected] | 5.4 | 0.60% | 2020-12-25 | 2026-06-16 |
| CVE-2020-35704 | Daybyday 2.1.0 allows stored XSS via the Title parameter to the New Lead screen. | [email protected] | 5.4 | 0.60% | 2020-12-25 | 2026-06-16 |