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 imperson…

published 2020-03-02 6y ago modified 2026-06-17 4mo ago also EUVD-2020-26701

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits: 0; none known

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.

Is CVE-2020-5539 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD	2.0	6.4	AV:N/AC:L/Au:N/C:P/I:P/A:N

Affected products

GRANDIT CORPORATION GRANDIT

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key

References

grandit.jp /etc/20200228_letter.pdf
vendor-advisory
jvn.jp /en/jp/JVN73472345/index.html
third-party-advisory

Sources

CVE List CVE-2020-5539
NVD CVE-2020-5539

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.