CVE-2023-41323
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 · uneditedGLPI 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. An unauthenticated user can enumerate users logins. Users are advised to upgrade to version 10.0.10. There are no known workarounds for this vulnerability.
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 confidenceGLPI versions prior to 10.0.10 contain an unauthenticated user enumeration vulnerability that allows remote attackers to discover valid user login names through the application. This information disclosure could facilitate subsequent attacks such as brute force credential theft or targeted phishing campaigns.
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>= 0.68, < 10.0.10CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GLPI installationCheck if GLPI is running in your environment by accessing the web application or checking for GLPI-related processes/web server configurations. Look for the login page typically found at /glpi/ or /front/login.phpAffected if GLPI is installed and accessible as a web application
-
Determine installed GLPI versionLocate the version file: check for a VERSION.php or version.txt file in the GLPI root directory, or access /ajax/update.php?action=getVersion via HTTP if the web interface is accessibleAffected if The version cannot be determined or is below 10.0.10
-
Compare version against affected rangeReview the identified version number. Affected versions are >= 0.68 and < 10.0.10. If your version is 10.0.10 or later, it is NOT affected. Versions 0.68 through 10.0.9 ARE affected.Affected if The installed version is 10.0.9 or lower, or any version between 0.68 and 10.0.9 inclusive
-
Verify unauthenticated access to GLPIConfirm the GLPI login page is accessible without authentication by attempting to reach the login URL from an unauthenticated network perspective. This is a pre-requisite for exploitation.Affected if The GLPI login page is accessible without credentials (which is the default configuration)
You are affected if GLPI is running and the installed version is 10.0.9 or lower (any version from 0.68 through 10.0.9), as this allows unauthenticated attackers to enumerate valid user login names through the application.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10
Upgrade GLPI to version 10.0.10 or later. No workarounds are available, making the upgrade mandatory for remediation.
10.0.10
- Create a complete backup of the GLPI database
- Create a backup of the existing GLPI installation directory
- Download GLPI version 10.0.10 from the official source (github.com/GLPIProject/glpi)
- Extract the new version files
- Replace the existing GLPI files with the new version files
- Run the GLPI update process by accessing the application URL
- Verify the upgrade was successful by logging in and checking the version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-41323 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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