CVE-2022-22113: In DayByDay CRM, versions 2.2.0 through 2.2.1 (latest) are vulnerable to Insufficient Session Expiration

This month

HIGH 8.8UPGRADE

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

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.0% (top 36%)
CISA exploited list	No
Weakness	CWE-613
Published	2022-01-13
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-13 09:15 UTCPublished CVE record published
2026-06-17 04:27 UTCUpdated Record last modified

daybydaycrm daybyday UPGRADE

Affected: >= 2.2.0 and <= 2.2.1

Fixed in: newer than 2.2.1

Safe to downgrade to: a release before 2.2.0

1. Check installed version

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

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

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade daybyday

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 2.2.0 (Debian / Ubuntu)

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

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

dnf --showduplicates list daybyday sudo dnf downgrade daybyday-<VERSION_BEFORE_2.2.0> sudo dnf versionlock add daybyday

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-22113?

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

Is CVE-2022-22113 being exploited?

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

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

How urgent is CVE-2022-22113?

Priority 52/100. High severity; Public exploit reference

Related CVEs

CVE-2022-22112 MEDIUM 5.4 UPGRADE In DayByDay CRM, versions 1.1 through 2.2.1 (latest) suffer from an application-wide Client-Side Template Inje
CVE-2020-35707 MEDIUM 5.4 DOWNGRADE Daybyday 2.1.0 allows stored XSS via the Company Name parameter to the New Client screen.
CVE-2020-35706 MEDIUM 5.4 DOWNGRADE Daybyday 2.1.0 allows stored XSS via the Title parameter to the New Project screen.
CVE-2020-35705 MEDIUM 5.4 DOWNGRADE Daybyday 2.1.0 allows stored XSS via the Name parameter to the New User screen.
CVE-2020-35704 MEDIUM 5.4 DOWNGRADE Daybyday 2.1.0 allows stored XSS via the Title parameter to the New Lead screen.

References

← Back to latest CVEs