DayByDay CRM - Weak Password Requirements in Update User
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Bottelet | DaybydayCRM | affected |
|
|||||||||
| Bottelet | flarepoint | affected |
|
No data.
No data available yet.
Vendor Solution
Update to 2.2.1
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-0541 | 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. |
Github GHSA |
GHSA-96v6-hrwg-p378 | Weak Password Requirements in Daybyday CRM |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.159% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.