dbcve.org
GlpiApplication · Glpi Project

CVE-2022-39376

MEDIUM · 6.5 CVSS v3.1 Published 2022-11-03
Fix available
A fix is available. Upgrade to 10.0.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
GLPI stands for Gestionnaire Libre de Parc Informatique. GLPI is a Free Asset and IT Management Software package that provides ITIL Service Desk features, licenses tracking and software auditing. Users may be able to inject custom fields values in `mailto` links. This issue has been patched, please upgrade to version 10.0.4. There are currently no known workarounds.

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 confidence

GLPI versions prior to 10.0.4 contain an injection vulnerability where user-controlled custom field values can be injected into mailto links. This likely allows attackers to manipulate the recipient, subject, or body of emails generated through the application, potentially leading to phishing attacks or execution of malicious content in vulnerable email clients.

MitigationUpgrade GLPI to version 10.0.4 or later to remediate this vulnerability. No workarounds are available.

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
GlpiApplication
Affected:>= 0.65, < 10.0.4

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify GLPI installation and version
    Locate the GLPI installation directory and check the version.php or version file typically found in the root directory or inc/ folder. The version is often defined in a constant like GLPI_VERSION.
    Affected if The installed version is 0.65 or higher but lower than 10.0.4
  2. Compare version to affected range
    Parse the version number found and compare it numerically against the affected range: >= 0.65 and < 10.0.4. Any version in this range is vulnerable.
    Affected if The installed version falls within >= 0.65 and < 10.0.4
  3. Confirm custom fields (custom profiles, user custom fields, or entity custom fields) feature is in use
    Check if any custom field definitions exist in the database tables like glpi_profiles_users (if custom profiles are used), or check if the custom fields plugin/module is enabled in the GLPI configuration. Look for tables prefixed with custom in the database.
    Affected if Custom field features are enabled and actively storing user-controlled values in the GLPI database
  4. Verify mailto link generation from custom fields
    Inspect the email template or notification configuration where custom field values are used in constructing mailto links. Check if custom field values are being directly inserted into mailto href attributes without proper sanitization.
    Affected if Custom field values are being used to dynamically generate mailto links in notifications, templates, or generated emails

A user is affected if GLPI version is 0.65 or higher but lower than 10.0.4, and custom field values are being used in mailto link generation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.4 or later
Fixed in 10.0.4
Interim mitigation

Upgrade GLPI to version 10.0.4 or later to remediate this vulnerability. No workarounds are available.

Recommended fix High confidence

GLPI 10.0.4

  1. Create a complete backup of the GLPI database and files
  2. Download GLPI version 10.0.4 from the official source
  3. Replace the existing GLPI installation files with the new version 10.0.4 files
  4. Run the GLPI upgrade script or navigate to the GLPI URL to trigger the database upgrade process
  5. Verify the installation was successful by logging in and checking that custom fields work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39376 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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