dbcve.org
ReportsApplication · Glpi Project

CVE-2022-39181

MEDIUM · 6.1 CVSS v3.1 Published 2022-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 - Reports plugin for GLPI Reflected Cross-Site-Scripting (RXSS). Type 1: Reflected XSS (or Non-Persistent) - The server reads data directly from the HTTP request and reflects it back in the HTTP response. Reflected XSS exploits occur when an attacker causes a victim to supply dangerous content to a vulnerable web application, which is then reflected back to the victim and executed by the web browser. The most common mechanism for delivering malicious content is to include it as a parameter in a URL that is posted publicly or emailed directly to the victim. URLs constructed in this manner constitute the core of many phishing schemes, whereby an attacker convinces a victim to visit a URL that refers to a vulnerable site. After the site reflects the attacker's content back to the victim, the content is executed by the victim's browser.

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

A reflected cross-site scripting (XSS) vulnerability exists in the GLPI Reports plugin. The vulnerability allows an attacker to inject malicious JavaScript through URL parameters, which the server reflects back in the HTTP response without proper sanitization or output encoding. When a victim visits the crafted URL, the attacker's script executes in their browser.

MitigationImplement proper input validation on all user-supplied parameters and apply output encoding (contextual escaping) when reflecting data back in HTTP responses. Additionally, configure Content Security Policy (CSP) headers to mitigate XSS execution.

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
ReportsApplication
Affected:all versions

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Verify if Reports plugin is installed
    Log into GLPI as administrator, navigate to Setup > Plugins. Look for 'Reports' or 'GLPI Reports' in the installed plugins list and check its status (installed/enabled).
    Affected if The Reports plugin is installed and enabled in GLPI.
  2. Identify Reports plugin version
    In the Plugins page, check the version column for the Reports plugin. Since all versions are affected, any installed version indicates potential exposure.
    Affected if The Reports plugin version is any version (all versions are affected per CVE).
  3. Review HTTP responses for unsanitized parameters
    Capture HTTP traffic or view page source while accessing Reports plugin pages with URL parameters (e.g., ?name=test, ?id=1). Check if parameter values are reflected in the HTML response without encoding.
    Affected if URL parameter values are reflected in the response without HTML entity encoding (e.g., <script> tags execute or special characters like < > " are not converted to &lt; &gt; &quot;).
  4. Inspect plugin source code for output encoding
    Locate plugin PHP files (typically in glpi/plugins/reports/ folder). Search for code that handles URL parameters and outputs them directly to HTML using echo, print, or similar functions without using htmlspecialchars() or equivalent encoding functions.
    Affected if Code outputs $_GET, $_POST, or $_REQUEST parameters directly to HTML without sanitization functions.

A defender is affected if the GLPI Reports plugin is installed and enabled, as all versions contain the reflected XSS vulnerability in how URL parameters are handled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation on all user-supplied parameters and apply output encoding (contextual escaping) when reflecting data back in HTTP responses. Additionally, configure Content Security Policy (CSP) headers to mitigate XSS execution.

Fix this in Reports Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39181 — 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-39181 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