CVE-2022-22110: In Daybyday CRM, versions 1.1 through 2.2.0 enforce weak password requirements in the user update functionalit

This month

HIGH 7.5REMOTEUPGRADE

CVE-2022-22110 is a high-severity flaw (CVSS 7.5) affecting daybyday crm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 33%)
CISA exploited list	No
Weakness	CWE-521
Published	2022-01-05
Last modified	2026-06-17

Publisher (CNA): Mend · Vendor: daybydaycrm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-01-05 15:15 UTCPublished CVE record published
2026-06-17 04:27 UTCUpdated Record last modified

daybydaycrm daybyday crm UPGRADE

Affected: >= 1.1.0 and <= 2.2.0

Fixed in: newer than 2.2.0

Safe to downgrade to: a release before 1.1.0

1. Check installed version

apt-cache policy daybyday-crm || rpm -q daybyday-crm || daybyday-crm --version

2. UPGRADE to newer than 2.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade daybyday-crm

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade daybyday-crm

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.1.0 (Debian / Ubuntu)

apt-cache madison daybyday-crm sudo apt install daybyday-crm=<VERSION_BEFORE_1.1.0> sudo apt-mark hold daybyday-crm

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list daybyday-crm sudo dnf downgrade daybyday-crm-<VERSION_BEFORE_1.1.0> sudo dnf versionlock add daybyday-crm

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-22110?

daybyday crm: upgrade to newer than 2.2.0. Exact commands for each OS are on this page.

Is CVE-2022-22110 being exploited?

CVE-2022-22110 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-22110 affect?

CVE-2022-22110 affects daybyday crm. Severity is high (CVSS 7.5). 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 chara

How urgent is CVE-2022-22110?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-22111 HIGH 8.8 DOWNGRADE In DayByDay CRM, version 2.2.0 is vulnerable to missing authorization
CVE-2022-22109 MEDIUM 5.4 DOWNGRADE In Daybyday CRM, version 2.2.0 is vulnerable to Stored Cross-Site Scripting (XSS) vulnerability that allows lo
CVE-2022-22108 MEDIUM 4.3 UPGRADE In Daybyday CRM, versions 2.0.0 through 2.2.0 are vulnerable to Missing Authorization
CVE-2022-22107 MEDIUM 4.3 UPGRADE In Daybyday CRM, versions 2.0.0 through 2.2.0 are vulnerable to Missing Authorization

References

← Back to latest CVEs