dbcve.org
GranditApplication

CVE-2020-5539

MEDIUM · 6.5 CVSS v3.1 Published 2020-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

GRANDIT versions 1.6 through 3.0 contain a session management vulnerability where the application does not properly manage user sessions. This allows remote attackers to impersonate legitimate users by hijacking or fixing sessions, enabling unauthorized access to alter or disclose sensitive information.

MitigationImplement proper session management including secure session ID generation, session invalidation on logout, session timeout, and protection against session fixation/hijacking. Apply vendor-supplied patches for all affected versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GranditApplication
Affected:= 1.6= 2.0= 2.1= 2.2= 2.3= 3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed GRANDIT version
    Access the GRANDIT administration console or check the application version information typically found in the system settings, About page, or version file within the GRANDIT installation directory
    Affected if The installed version matches 1.6, 2.0, 2.1, 2.2, 2.3, or 3.0 from the affected versions list
  2. Verify session ID generation method
    Examine the session configuration files or code that generates session identifiers. Check if session IDs are randomly generated with sufficient entropy or if they follow predictable patterns
    Affected if Session IDs are generated using weak or predictable methods such as sequential numbers, timestamp-based values, or insufficient randomness
  3. Check session fixation protection
    Review the application code or configuration to determine whether the session ID is regenerated upon user authentication. Look for session ID regeneration logic after login
    Affected if The application does not regenerate session IDs after authentication, allowing attackers to fix a session ID before the victim logs in
  4. Verify session invalidation on logout
    Test the logout functionality by logging in, capturing a session ID, logging out, and then attempting to reuse the original session ID to access protected resources
    Affected if The original session remains valid after logout, allowing session reuse by attackers
  5. Check session timeout configuration
    Review the session timeout settings in the application configuration or server settings. Determine if there is a reasonable timeout period for idle sessions
    Affected if Sessions do not timeout or have an excessively long timeout period, increasing the window for session hijacking attacks

A user is affected if they are running GRANDIT versions 1.6 through 3.0 AND the application lacks proper session management controls such as secure session ID generation, session regeneration on login, session invalidation on logout, or appropriate session timeouts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper session management including secure session ID generation, session invalidation on logout, session timeout, and protection against session fixation/hijacking. Apply vendor-supplied patches for all affected versions.

Fix this in Grandit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5539 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-5539 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data