CVE-2023-41888
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. The lack of path filtering on the GLPI URL may allow an attacker to transmit a malicious URL of login page that can be used to attempt a phishing attack on user credentials. 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 · high confidenceThis is an open redirect vulnerability in GLPI where the application lacks proper path filtering on URLs. An attacker can craft malicious URLs that appear to originate from the legitimate GLPI login page but redirect users to external phishing sites to steal credentials.
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>= 10.0.8, < 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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Locate GLPI installation directorySearch for common GLPI installation paths such as /var/www/html/glpi, /opt/glpi, or the web root directory. Check for the presence of glpi/ or files like index.php, ajax/ticket.php, or config.php at typical web server locations.Affected if GLPI is found in the environment
-
Identify GLPI version from filesCheck for a version file in the GLPI root directory. Look for a file named version, VERSION, or examine the content of src/DbUtils.php for a version constant. You may also find version info in the config/config_db.php file or in a composer.json if present.Affected if A version file exists and shows a version number
-
Compare installed version to affected rangeCompare the identified version against the affected range: >= 10.0.8 and < 10.0.10. If the version is 10.0.8, 10.0.9, or any 10.0.x version below 10.0.10, the installation is vulnerable.Affected if The version falls within >= 10.0.8 and < 10.0.10
-
Check if web interface is accessibleVerify the GLPI login page is accessible over HTTP/HTTPS by accessing the main URL. The open redirect vulnerability can be triggered through the login page redirect parameter.Affected if The GLPI web interface is publicly or internally accessible and the version is within the affected range
A user is affected if GLPI version 10.0.8 or 10.0.9 is installed and the web interface is accessible, allowing malicious redirect URLs to be crafted from the login page.
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. No workarounds are available.
10.0.10
- Back up the current GLPI database and files
- Download GLPI version 10.0.10 from the official GLPI repository or website
- Extract the new version files to the web server document root
- Run the GLPI upgrade process by accessing the application in a web browser
- Follow the on-screen upgrade wizard instructions
- Verify the installation by logging in and checking core functionality
- Ensure the version is reported as 10.0.10 in the administration panel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41888 — 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-41888 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