dbcve.org
GlpiApplication · Glpi Project

CVE-2025-21627

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-25
Fix available
A fix is available. Upgrade to 10.0.18 or later.
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 is a free asset and IT management software package. In versions prior to 10.0.18, a malicious link can be crafted to perform a reflected XSS attack on the search page. If the anonymous ticket creation is enabled, this attack can be performed by an unauthenticated user. Version 10.0.18 contains a fix for the issue.

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

This is a reflected XSS vulnerability in GLPI's search page affecting versions prior to 10.0.18. An attacker can craft a malicious link containing JavaScript payloads that execute in the victim's browser when visited. If anonymous ticket creation is enabled, unauthenticated users can exploit this vulnerability without any authentication.

MitigationUpgrade to GLPI version 10.0.18 or later which contains the fix. As a compensating control, disable anonymous ticket creation if not required, and consider implementing WAF rules to detect and block XSS patterns in URL parameters.

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:< 10.0.18

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. Determine installed GLPI version
    Locate the version.php file in the GLPI root directory (e.g., /var/www/html/glpi/version.php) and read the $CFG_GLPI['version'] value, or log into GLPI as administrator and navigate to Setup > General > System to view the version information.
    Affected if The installed version is below 10.0.18 (e.g., 10.0.17, 10.0.16, 10.0.15, etc.)
  2. Check if anonymous ticket creation is enabled
    Log into GLPI as an administrator, navigate to Setup > General > Assistance tab, and look for the 'Allow anonymous ticket creation' setting. Alternatively, check the database table glpi_configs for the field 'allow_anonymous_ticket' set to value 1.
    Affected if Anonymous ticket creation is enabled (value = 1), which allows unauthenticated attackers to exploit the XSS vulnerability.
  3. Identify the GLPI web root directory
    Locate the main GLPI installation directory on the web server. Common paths include /var/www/html/glpi, /usr/share/glpi, or C:\xampp\htdocs\glpi on Windows. Check your web server configuration (Apache/nginx) for the DocumentRoot pointing to GLPI.
    Affected if This step confirms the installation location for version verification - if the version.php file cannot be found, the GLPI installation may be non-standard or compromised.

You are affected if your GLPI version is below 10.0.18 AND anonymous ticket creation is enabled, allowing unauthenticated users to trigger the reflected XSS via malicious links to the search page.

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.18 or later
Fixed in 10.0.18
Interim mitigation

Upgrade to GLPI version 10.0.18 or later which contains the fix. As a compensating control, disable anonymous ticket creation if not required, and consider implementing WAF rules to detect and block XSS patterns in URL parameters.

Recommended fix High confidence

GLPI 10.0.18

  1. 1. Back up your existing GLPI database and files before proceeding with any upgrade.
  2. 2. Download GLPI version 10.0.18 from the official GLPI repository or website.
  3. 3. Replace the existing GLPI files with the new version 10.0.18 files, preserving your configuration and data.
  4. 4. Run the GLPI upgrade process by accessing the application in a web browser (e.g., navigate to your GLPI URL/glpi).
  5. 5. Follow the on-screen upgrade wizard prompts to complete the migration to version 10.0.18.
  6. 6. Verify that the upgrade was successful by logging in and checking the GLPI version number.
  7. 7. Test the search functionality to confirm the XSS vulnerability is no longer present.
Caveat Standard upgrade - review release notes for any minor configuration changes between your current version and 10.0.18

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

Fix this in Glpi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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