CVE-2020-35705: Daybyday 2.1.0 allows stored XSS via the Name parameter to the New User screen.

Routine

MEDIUM 5.4DOWNGRADE

CVE-2020-35705 is a medium-severity flaw (CVSS 5.4) affecting daybyday. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Daybyday 2.1.0 allows stored XSS via the Name parameter to the New User screen.

Why this priority

Public exploit reference

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

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-79
Published	2020-12-25
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: daybydaycrm

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

Am I affected?

Timeline

2020-12-25 06:15 UTCPublished CVE record published
2026-06-17 03:14 UTCUpdated Record last modified

daybydaycrm daybyday DOWNGRADE

Affected: 2.1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.1.0

1. Check installed version

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

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

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

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

dnf --showduplicates list daybyday sudo dnf downgrade daybyday-<VERSION_BEFORE_2.1.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-2020-35705?

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

Is CVE-2020-35705 being exploited?

CVE-2020-35705 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-2020-35705 affect?

CVE-2020-35705 affects daybyday. Severity is medium (CVSS 5.4). Daybyday 2.1.0 allows stored XSS via the Name parameter to the New User screen.

How urgent is CVE-2020-35705?

Priority 36/100. Public exploit reference

Related CVEs

CVE-2022-22113 HIGH 8.8 UPGRADE In DayByDay CRM, versions 2.2.0 through 2.2.1 (latest) are vulnerable to Insufficient Session Expiration
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-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