dbcve.org
GlpiApplication · Glpi Project

CVE-2025-53008

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-30
Fix available
A fix is available. Upgrade to 10.0.19 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 is a Free Asset and IT Management Software package, that provides ITIL Service Desk features, licenses tracking and software auditing. In versions 9.3.1 through 10.0.19, a connected user can use a malicious payload to steal mail receiver credentials. This is fixed in version 10.0.19.

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 · high confidence

GLPI versions 9.3.1 through 10.0.19 contain a vulnerability allowing an authenticated (connected) user to inject a malicious payload that steals mail receiver credentials. The flaw appears to involve improper handling of mail configuration parameters, enabling credential exfiltration.

MitigationUpdate GLPI to version 10.0.19 or later to apply the vendor patch. Review mail receiver configurations after patching to ensure credentials were not previously compromised.

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:>= 9.3.1, < 10.0.19

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
    Access the GLPI web interface and navigate to Setup > General > System, or check the version file in the GLPI installation directory (typically version.txt or similar). Compare against the affected range: 9.3.1 through 10.0.19.
    Affected if Installed version is 9.3.1, 10.0.x before 10.0.19, or any version within this range.
  2. Identify mail receiver configurations
    Navigate to Setup > Notifications > Mail receivers in the GLPI admin panel. Check if any mail receivers are configured (email accounts used to receive tickets).
    Affected if Mail receivers are configured and the GLPI version is within the affected range.
  3. Review mail receiver account credentials
    Inspect each configured mail receiver for unexpected or suspicious parameters, particularly in fields related to username, password, or server URLs. Look for unexpected external domains or credential-related placeholders.
    Affected if Credentials contain unexpected values, additional accounts exist that were not created by administrators, or unusual server paths are present.
  4. Check for recent unauthorized access
    Review GLPI login logs (Setup > Maintenance > Logs or external web server logs) for any suspicious authenticated activity around mail configuration pages from users who should not have modified those settings.
    Affected if Unusual authenticated activity is found related to mail receiver configuration pages.

User is affected if GLPI version is 9.3.1 through 10.0.19 and mail receivers are configured with potentially exfiltrated credentials.

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.19 or later
Fixed in 10.0.19
Interim mitigation

Update GLPI to version 10.0.19 or later to apply the vendor patch. Review mail receiver configurations after patching to ensure credentials were not previously compromised.

Recommended fix High confidence

10.0.19

  1. 1. Back up your existing GLPI database and installation directory
  2. 2. Download GLPI version 10.0.19 from the official source (github.com/GLPI-project/glpi/releases)
  3. 3. Replace the existing GLPI files with the new version 10.0.19 files
  4. 4. Run the GLPI upgrade process by accessing your GLPI URL and following the on-screen upgrade wizard
  5. 5. Verify that the mail receiver credentials are now properly protected
Caveat Review release notes for any between-version changes before upgrading

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-2025-53008 — 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-53008 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