dbcve.org
GlpiApplication · Glpi Project

CVE-2021-39210

MEDIUM · 6.5 CVSS v3.1 Published 2021-09-15
Fix available
A fix is available. Upgrade to 9.5.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
GLPI is a free Asset and IT management software package. In versions prior to 9.5.6, the cookie used to store the autologin cookie (when a user uses the "remember me" feature) is accessible by scripts. A malicious plugin that could steal this cookie would be able to use it to autologin. This issue is fixed in version 9.5.6. As a workaround, one may avoid using the "remember me" feature.

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 · high confidence

GLPI versions prior to 9.5.6 expose the autologin cookie (used by the 'remember me' feature) to scripts, allowing malicious plugins to steal the cookie and perform unauthorized autologin as any user.

MitigationUpgrade GLPI to version 9.5.6 or later, which properly secures the autologin cookie. As a temporary workaround, disable the 'remember me' feature until the upgrade is completed.

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
GlpiApplication
Affected:< 9.5.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Determine installed GLPI version
    Locate the version.php file in the GLPI root directory (typically at /glpi/version.php) or access the administration panel under Setup > General > System Information. Extract the version number from the 'glpi_version' variable.
    Affected if The installed version number is less than 9.5.6 (for example, 9.5.5, 9.5.4, etc.)
  2. Verify if remember me autologin is enabled
    Access the GLPI configuration panel as an administrator. Navigate to Setup > General > Authentication settings. Look for the 'Remember me' or 'Auto-login' option and check whether it is activated.
    Affected if The 'Remember me' or autologin feature is currently enabled in the GLPI authentication settings.
  3. Identify installed plugins
    Access the GLPI administration panel and navigate to Setup > Plugins. Review the list of all installed plugins, noting any third-party or non-bundled plugins that are active.
    Affected if Any plugins are installed and active, particularly third-party plugins from untrusted sources, as these scripts can potentially access the exposed autologin cookie.

You are affected if your GLPI version is below 9.5.6 AND the remember me feature is enabled AND you have any plugins installed that could access the cookie.

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.

dbcve · scoped
Upgrade available Upgrade to 9.5.6 or later
Fixed in 9.5.6
Interim mitigation

Upgrade GLPI to version 9.5.6 or later, which properly secures the autologin cookie. As a temporary workaround, disable the 'remember me' feature until the upgrade is completed.

Recommended fix High confidence

9.5.6

  1. 1. Back up the existing GLPI database and files
  2. 2. Download GLPI version 9.5.6 from the official GLPI repository (glpi-project.org)
  3. 3. Extract the new version files
  4. 4. Replace the existing GLPI installation files with the new version 9.5.6 files
  5. 5. Run the GLPI upgrade process by accessing the application in a web browser
  6. 6. Verify the installation is working correctly
  7. 7. Ensure the 'remember me' functionality now uses HttpOnly cookies

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-39210 — 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-2021-39210 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