CVE-2021-39213
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 · uneditedGLPI is a free Asset and IT management software package. Starting in version 9.1 and prior to version 9.5.6, GLPI with API Rest enabled is vulnerable to API bypass with custom header injection. This issue is fixed in version 9.5.6. One may disable API Rest as a workaround.
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 confidenceGLPI versions 9.1 through 9.5.5 with the REST API enabled contain an API bypass vulnerability that allows attackers to inject custom headers to circumvent authentication or authorization controls in the API. This enables unauthorized access to GLPI assets and IT management functions.
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>= 9.1, < 9.5.6CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify GLPI installation versionLocate the GLPI version by checking the config file (typically config/config.php or config/DB.php), the login page footer, or by querying the API endpoint /apirest.php?apiver= - compare the installed version against the affected range of >= 9.1 and < 9.5.6Affected if The installed version is 9.1, 9.2, 9.3, 9.4, 9.5, 9.5.1, 9.5.2, 9.5.3, 9.5.4, or 9.5.5 (any version from 9.1 up to but not including 9.5.6)
-
Confirm REST API is enabledLog into the GLPI administrative interface and navigate to Setup > General > API, or check the configuration file for the API plugin/restapi settings - verify whether the REST API feature is turned onAffected if The REST API is enabled and accessible at /apirest.php or /api/index.php endpoints
-
Verify API accessibilityAttempt a curl request to the API endpoint (such as curl -k https://TARGET/apirest.php) - if the API responds with any JSON or authentication challenge, the API is activeAffected if The API endpoint returns any HTTP response (including 401/403 auth challenges), indicating the API is listening
The environment is affected only if GLPI version is 9.1 through 9.5.5 AND the REST API feature is currently enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.5.6
Upgrade GLPI to version 9.5.6 or later, or temporarily disable the REST API feature as a workaround until patching can be completed.
GLPI 9.5.6
- Upgrade GLPI to version 9.5.6 or later to resolve the API bypass vulnerability
- Alternatively, as a temporary mitigation, disable the REST API by setting the configuration option to disable API access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-39213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-39213 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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