dbcve.org
ManageentitiesApplication · Glpi Project

CVE-2022-34127

HIGH · 7.5 CVSS v3.1 Published 2023-04-16
Fix available
A fix is available. Upgrade to 4.0.2 or later.
See remediation →
84/100
Remediation priority · High
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
The Managentities plugin before 4.0.2 for GLPI allows reading local files via directory traversal in the inc/cri.class.php file parameter.

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

The Managentities plugin before version 4.0.2 for GLPI contains a directory traversal vulnerability in the inc/cri.class.php file. Attackers can manipulate the file parameter to read arbitrary local files from the server filesystem, potentially exposing sensitive configuration files, credentials, or other system data.

MitigationUpdate the Managentities plugin to version 4.0.2 or later to receive the security patch. If immediate update is not possible, consider disabling the plugin or restricting access to the affected functionality via network-level controls.

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
ManageentitiesApplication
Affected:< 4.0.2

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Manageentities plugin is installed
    Navigate to GLPI administration panel, go to Setup > Plugins, and look for 'Manageentities' or 'Managemententites' in the installed plugins list
    Affected if The plugin appears in the plugins list and is enabled
  2. Check the installed plugin version
    In the Plugins page of GLPI admin panel, locate the version column for the Manageentities plugin entry
    Affected if The version shown is lower than 4.0.2 (for example 4.0.1, 4.0.0, or any version prior)
  3. Verify vulnerable file exists
    On the server filesystem, check for the presence of the file inc/cri.class.php within the Manageentities plugin directory path (typically at glpi/plugins/manageentities/inc/cri.class.php)
    Affected if The file exists at that path and the plugin version is below 4.0.2
  4. Confirm plugin is enabled
    In GLPI admin panel, verify the Manageentities plugin status shows as 'Enabled' rather than disabled or uninstalled
    Affected if The plugin is enabled and the version is below 4.0.2

The environment is affected if the Manageentities plugin is installed, enabled, and its version is lower than 4.0.2, with the vulnerable inc/cri.class.php file present.

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 4.0.2 or later
Fixed in 4.0.2
Interim mitigation

Update the Managentities plugin to version 4.0.2 or later to receive the security patch. If immediate update is not possible, consider disabling the plugin or restricting access to the affected functionality via network-level controls.

Recommended fix High confidence

4.0.2

  1. Create a full backup of your GLPI database and the Manageentities plugin directory before proceeding
  2. Download Manageentities plugin version 4.0.2 from the official GLPI plugin repository or the developer's distribution channel
  3. Log in to GLPI as an administrator with sufficient privileges
  4. Navigate to the Plugins section in GLPI administration
  5. Uninstall the current vulnerable version of the Manageentities plugin (versions prior to 4.0.2)
  6. Remove the existing plugin files from the server's plugins directory
  7. Extract and install the downloaded version 4.0.2 of the Manageentities plugin
  8. Verify the installation completed successfully by checking the plugin version in GLPI

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

Fix this in Manageentities Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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