basicsecurity.net
Proof, not just disclosure.
Threats / Teclib / CVE-2022-35914
CVE-2022-35914 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-073EPSS 0.99521 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
715 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99521 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Teclib, GLPI. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-74 CWE-74 — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-74 · CWE-74Injection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 715 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.