CVE-2022-34125
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 · uneditedfront/icon.send.php in the CMDB plugin before 3.0.3 for GLPI allows attackers to gain read access to sensitive information via a _log/ pathname in the 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 · high confidenceA path traversal vulnerability in the CMDB plugin for GLPI (front/icon.send.php before version 3.0.3) allows attackers to read sensitive files by manipulating the file parameter with a _log/ pathname, enabling unauthorized access to configuration files, credentials, or other sensitive data stored on the server.
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< 3.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify CMDB plugin installationLocate the CMDB plugin directory in the GLPI plugins folder (typically plugins/cmdb/) and identify the installed version from the plugin's info.json, setup.php, or version fileAffected if The CMDB plugin is present and its version is below 3.0.3
-
Check for vulnerable file presenceExamine if the file front/icon.send.php exists within the CMDB plugin directoryAffected if The file front/icon.send.php exists in the CMDB plugin, indicating the vulnerable component is present
-
Inspect file parameter handlingReview the source code of front/icon.send.php to confirm whether the 'file' parameter is processed without proper sanitization of path traversal sequencesAffected if The code accepts user-supplied file parameter and uses it in file operations without validating for '../' or '_log/' sequences
-
Confirm plugin is enabledCheck GLPI plugin configuration or database to verify whether the CMDB plugin is actively enabledAffected if The CMDB plugin is enabled and accessible to users
The environment is affected if the CMDB plugin for GLPI is installed and enabled with a version lower than 3.0.3, and the vulnerable front/icon.send.php file exists in the plugin directory.
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 · scoped3.0.3
Update the CMDB plugin to version 3.0.3 or later to obtain the vendor patch. Alternatively, implement strict input validation on the file parameter to reject path traversal sequences and restrict file access to allowed directories.
CMDB plugin version 3.0.3 or later for GLPI
- 1. Backup your GLPI instance and database before making any changes
- 2. Navigate to the GLPI plugin management interface
- 3. Locate the CMDB plugin in the list of installed plugins
- 4. Update the CMDB plugin to version 3.0.3 or later
- 5. Verify the update was successful by checking the plugin version
- 6. Test that the icon.send.php functionality works correctly and the vulnerability is no longer exploitable
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-2022-34125 — 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-2022-34125 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