CVE-2022-35914
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/vendor/htmlawed/htmlawed/htmLawedTest.php in the htmlawed module for GLPI through 10.0.2 allows PHP code injection.
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 confidenceThe htmlawed vendor module's htmLawedTest.php file in GLPI through version 10.0.2 contains a PHP code injection vulnerability that allows remote attackers to execute arbitrary PHP code on the server via the exposed test endpoint.
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<= 10.0.2CVSS 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.
-
Check GLPI versionLocate the version.php or VERSION file in the GLPI root directory (e.g., /var/www/glpi/VERSION or version.php) and read the version numberAffected if The installed version is 10.0.2 or lower
-
Locate the vulnerable test fileCheck for the presence of htmLawedTest.php in the vendor directory. Common paths: /vendor/glpi-project/htmldiff/htmLawedTest.php or /vendor/htmLawed/htmLawedTest.phpAffected if The file htmLawedTest.php exists in the vendor directory
-
Verify vendor directory is web-accessibleAttempt to access http://yourdomain/vendor/glpi-project/htmldiff/htmLawedTest.php or the corresponding htmLawed path via HTTP from an external host, or check web server configuration for Alias or RewriteRule directives that allow access to /vendorAffected if The vendor directory or the htmLawedTest.php file is reachable via HTTP/HTTPS from the internet or untrusted networks
-
Check web server document root configurationReview the web server (Apache/Nginx) configuration files to see if the vendor directory is explicitly blocked or allowed. Look for directives like 'AllowOverride None' on /vendor paths or location blocks for /vendorAffected if The vendor directory is not explicitly denied in the web server configuration, allowing potential access to the test file
You are affected if GLPI version is 10.0.2 or lower AND the htmLawedTest.php file exists in the vendor directory AND that directory is web-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 · scopedRemove or disable access to the htmLawedTest.php file (a test/debug script that should not be in production), and update GLPI to version 10.0.3 or later which includes the patched htmlawed library.
GLPI 10.0.3 or later
- Download GLPI version 10.0.3 or later from the official GLPI project website (glpi-project.org)
- Back up your existing GLPI database and files before upgrading
- Extract the new version files to your web server
- Run the GLPI upgrade process by accessing the application in your browser
- Verify that the /vendor/htmlawed/htmlawed/htmLawedTest.php file has been removed or secured in the new version
- Test that GLPI functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35914 — 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-35914 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