CVE-2022-34128
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 Cartography (aka positions) plugin before 6.0.1 for GLPI allows remote code execution via PHP code in the POST data to front/upload.php.
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 Cartography plugin (also known as positions) for GLPI versions prior to 6.0.1 contains an unauthenticated remote code execution vulnerability. Attackers can inject arbitrary PHP code through POST data submitted to the front/upload.php endpoint, allowing them to execute commands 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< 6.0.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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify Cartography plugin is installedLog in to GLPI as administrator, navigate to Setup > Plugins, and look for 'Cartography' or 'Positions' in the list of installed pluginsAffected if Plugin is not listed means not affected; if listed, continue to version check
-
Check installed plugin versionIn the Plugins page, note the version number displayed next to the Cartography/Positions plugin entry. Compare this version against 6.0.1Affected if Version shown is less than 6.0.1 (for example, 6.0.0, 5.x, or any earlier version)
-
Verify vulnerable endpoint existsCheck if the file /front/upload.php exists within the cartography plugin directory on the web server. The path is typically /glpi/plugins/cartography/front/upload.php or /glpi/plugins/positions/front/upload.phpAffected if File upload.php exists in the plugin's front directory
If the Cartography/Positions plugin is installed with a version below 6.0.1 and the front/upload.php endpoint is present, the environment is vulnerable to unauthenticated RCE via the described attack vector.
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 · scoped6.0.1
Update the Cartography plugin to version 6.0.1 or later to remediate this RCE vulnerability. If immediate patching is not possible, consider restricting access to the upload.php endpoint via network-level controls or web server configuration.
6.0.1
- 1. Create a full backup of the GLPI database and the Cartography plugin directory
- 2. Download the Cartography (positions) plugin version 6.0.1 from the official GLPI marketplace or the plugin's official repository
- 3. Navigate to GLPI administration panel > Plugins
- 4. Uninstall the vulnerable Cartography plugin if already installed
- 5. Remove the existing plugin files from the server (typically in glpi/plugins/positions/)
- 6. Extract and upload the new version 6.0.1 files to the plugins directory
- 7. Install and enable the plugin through the GLPI Plugins interface
- 8. Verify the upload functionality is working correctly and test that PHP code execution in uploads is now blocked
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34128 — 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-34128 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