Threats / Teclib / CVE-2022-35914
CVE-2022-35914
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Teclib GLPI vulnerability
Teclib GLPI contains a remote code execution vulnerability in the htmlawed third-party library, enabling unauthenticated attackers to execute arbitrary code on affected systems.
Verdict
Today item — known-exploited.
This is a critical remote code execution flaw in a widely-deployed IT asset management platform. The vulnerability has been actively exploited in the wild and carries a high EPSS score, indicating significant real-world risk to organizations using GLPI.
CISA KEV Yes · 2023-03-074EPSS 0.99696 (verify live)5Exploit Weaponized · public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
746 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-03-07).
Probability (EPSS)
EPSS 0.99696 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Teclib, GLPI. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-74 CWE-74 — weakness family: Injection.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 169 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious input that exploits improper neutralization in the htmlawed library to inject and execute arbitrary code.
Business
Attackers gain unauthorized code execution on the GLPI server, compromising the integrity and confidentiality of IT asset data and infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the code execution to establish persistence, escalate privileges, or pivot to other systems on the network.
Business
The organization faces potential lateral movement within its infrastructure, leading to broader compromise of connected systems and data loss.
3
Lateral reach — past segmentation narrative 3
Attacker
I exfiltrate sensitive configuration data, credentials, or asset inventory information stored in GLPI.
Business
Exposure of IT infrastructure details and credentials increases risk of follow-on attacks and regulatory compliance violations.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05