CVE-2020-5539: GRANDIT Ver.1.6, Ver.2.0, Ver.2.1, Ver.2.2, Ver.2.3, and Ver.3.0 do not properly manage sessions, which allows

This month

MEDIUM 6.5REMOTEDOWNGRADE

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

GRANDIT Ver.1.6, Ver.2.0, Ver.2.1, Ver.2.2, Ver.2.3, and Ver.3.0 do not properly manage sessions, which allows remote attackers to impersonate an arbitrary user and then alter or disclose the information via unspecified vectors.

Why this priority

Remotely exploitable, no login, no user action

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

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.8% (top 42%)
CISA exploited list	No
Weakness	CWE-639
Published	2020-03-02
Last modified	2026-06-17

Publisher (CNA): JPCERT/CC · Vendor: grandit

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

Am I affected?

Timeline

2020-03-02 08:15 UTCPublished CVE record published
2026-06-17 03:21 UTCUpdated Record last modified

grandit grandit DOWNGRADE

Affected: 1.6 · 2.0 · 2.1 · 2.2 · 2.3 · 3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.6

1. Check installed version

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

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

apt-cache madison grandit sudo apt install grandit=<VERSION_BEFORE_1.6> sudo apt-mark hold grandit

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

dnf --showduplicates list grandit sudo dnf downgrade grandit-<VERSION_BEFORE_1.6> sudo dnf versionlock add grandit

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

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

Is CVE-2020-5539 being exploited?

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

CVE-2020-5539 affects grandit. Severity is medium (CVSS 6.5). GRANDIT Ver.1.6, Ver.2.0, Ver.2.1, Ver.2.2, Ver.2.3, and Ver.3.0 do not properly manage sessions, which allows remote attackers to impersonate an arbitrary user and then alter or disclose the information via unspecified vectors.

How urgent is CVE-2020-5539?

Priority 42/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs