CVE-2022-34126
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 · uneditedThe Activity plugin before 3.1.1 for GLPI allows reading local files via directory traversal in the front/cra.send.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 · high confidenceThe Activity plugin for GLPI contains a directory traversal vulnerability in front/cra.send.php that allows unauthenticated attackers to read arbitrary local files on the server by manipulating the file parameter with path traversal sequences (e.g., ../../../../etc/passwd).
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.1.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Activity plugin installationLocate the Activity plugin directory in the GLPI plugins folder, or access GLPI administration panel to list installed pluginsAffected if Activity plugin is not installed or not listed in GLPI plugin management
-
Identify Activity plugin versionCheck the version file or manifest within the Activity plugin directory, or view plugin information in GLPI plugin management interfaceAffected if Version is less than 3.1.1 (e.g., 3.0.0, 3.0.1, 3.1.0)
-
Confirm vulnerable file presenceCheck if the file front/cra.send.php exists within the Activity plugin directory structureAffected if The file front/cra.send.php exists in the Activity plugin folder
-
Test vulnerable parameter accessibilityAttempt an HTTP request to the endpoint front/cra.send.php with a manipulated file parameter containing path traversal sequences (e.g., ?file=../../../../etc/passwd)Affected if The server returns content from files outside the intended directory, confirming the directory traversal is exploitable
A system is affected if the GLPI Activity plugin version is below 3.1.1 and the vulnerable endpoint front/cra.send.php is accessible, allowing unauthenticated path traversal via the file parameter.
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.1.1
Upgrade the Activity plugin to version 3.1.1 or later which contains the fix for this directory traversal vulnerability.
Activity plugin version 3.1.1
- Upgrade the Activity plugin for GLPI to version 3.1.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34126 — 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-34126 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