Is this vulnerability remotely exploitable?

Yes, but only by authenticated users. An attacker must be able to access GLPI over the network and authenticate as a technician (or another role with equivalent upload capabilities) to exploit the issue.

What level of access is required to exploit this vulnerability?

Exploitation requires a valid GLPI account with technician-level permissions that allow uploading files through the affected functionality. Anonymous or unauthenticated users cannot directly trigger this flaw under normal configurations.

What is the safest general fix pattern for this vulnerability class?

The safest pattern is to remove any dynamic object instantiation or deserialization driven by user-controlled data and replace it with explicit, whitelist-based logic. Uploaded files should be treated as passive data only, stored in non-executable locations, and never used as a source for class names, methods, or configuration directives.

Severity:

HIGH RISK

(8.0)

Unsafe PHP Object Instantiation (CWE-502) in GLPI Technician File Handling

CVE-2026-22248

Published:

Mar 11, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Unsafe Deserialization

CWE:

CWE-502

Impact:

Remote Code Execution by Authenticated User

Severity:

HIGH RISK

(8.0)

CVSS Version:

3.1

Vulnerability Type

Category:

Unsafe Deserialization

CWE:

CWE-502

Impact:

Remote Code Execution by Authenticated User

Severity:

HIGH RISK

(8.0)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Unsafe PHP Object Instantiation (CWE-502) in GLPI Technician File Handling

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal