dbcve.org
GlpiApplication · Glpi Project

CVE-2025-23046

HIGH · 7.5 CVSS v3.1 Published 2025-02-25
Fix available
A fix is available. Upgrade to 10.0.18 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 is a free asset and IT management software package. Starting in version 9.5.0 and prior to version 10.0.18, if a "Mail servers" authentication provider is configured to use an Oauth connection provided by the OauthIMAP plugin, anyone can connect to GLPI using a user name on which an Oauth authorization has already been established. Version 10.0.18 contains a patch. As a workaround, one may disable any "Mail servers" authentication provider configured to use an Oauth connection provided by the OauthIMAP plugin.

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.5.0 through 10.0.17 contain an authentication bypass vulnerability in the Mail servers authentication provider when using OAuth connections via the OauthIMAP plugin. An unauthenticated attacker can connect using any username on which an OAuth authorization has already been established, bypassing normal authentication controls.

MitigationUpgrade GLPI to version 10.0.18 or later, or disable any Mail servers authentication provider configured to use OauthIMAP plugin OAuth connections as a workaround.

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.5.0, < 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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed GLPI version
    Check the version.php file in the GLPI root directory, or access the GLPI system information page (Setup > System > Information) to view the installed version number
    Affected if Version is 9.5.0 through 10.0.17 (inclusive)
  2. Identify Mail servers authentication providers
    Navigate to Setup > Authentication > Authentication sources in the GLPI admin interface, and review any configured authentication providers of type 'Mail servers'
    Affected if A Mail servers authentication provider exists and is enabled
  3. Verify OAuth configuration for Mail servers auth
    In the authentication source configuration, examine whether OAuth is enabled and specifically check if the OauthIMAP plugin is selected as the connection method
    Affected if OAuth is enabled and OauthIMAP plugin is selected as the connection method
  4. Confirm OAuth authorization state
    Review user accounts or OAuth authorization records to determine if any OAuth authorizations have been established for mail accounts in the system
    Affected if At least one OAuth authorization exists for any user account

You are affected if your GLPI version is between 9.5.0 and 10.0.17 AND you have an active Mail servers authentication provider configured to use OAuth via the OauthIMAP plugin.

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 GLPI to version 10.0.18 or later, or disable any Mail servers authentication provider configured to use OauthIMAP plugin OAuth connections as a workaround.

Recommended fix High confidence

10.0.18

  1. Backup the GLPI database and files before proceeding with any changes
  2. Download GLPI version 10.0.18 from the official GLPI repository (github.com/glpi-project/glpi)
  3. Extract the downloaded archive and replace the existing GLPI files with the new version
  4. Follow standard GLPI upgrade procedure: run the install/migrate script if needed, or access GLPI to trigger automatic database migration
  5. Verify the installation by logging in and checking that the version displays as 10.0.18
  6. Alternatively, as a temporary workaround before upgrading: go to Configuration > Authentication > Authentification sources, locate any 'Mail servers' providers configured to use OAuth connections from the OauthIMAP plugin, and disable or remove them

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

Fix this in Glpi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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