CVE-2022-22111: In DayByDay CRM, version 2.2.0 is vulnerable to missing authorization

This month

HIGH 8.8DOWNGRADE

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

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.

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.0% (top 36%)
CISA exploited list	No
Weakness	CWE-862
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 DOWNGRADE

Affected: 2.2.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.2.0

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 2.2.0 (Debian / Ubuntu)

apt-cache madison daybyday-crm sudo apt install daybyday-crm=<VERSION_BEFORE_2.2.0> sudo apt-mark hold daybyday-crm

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list daybyday-crm sudo dnf downgrade daybyday-crm-<VERSION_BEFORE_2.2.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-22111?

daybyday crm: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-22111 being exploited?

CVE-2022-22111 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-22111 affect?

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

How urgent is CVE-2022-22111?

Priority 47/100. High severity

Related CVEs

CVE-2022-22110 HIGH 7.5 UPGRADE In Daybyday CRM, versions 1.1 through 2.2.0 enforce weak password requirements in the user update functionalit
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