CVE-2025-52897
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 is a Free Asset and IT Management Software package. In versions 9.1.0 through 10.0.18, an unauthenticated user can send a malicious link to attempt a phishing attack from the planning feature. 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 · moderate confidenceGLPI versions 9.1.0 through 10.0.18 contain a vulnerability in the planning feature that allows unauthenticated users to craft and send malicious links for phishing attacks. The vulnerability is exploitable without authentication and is resolved in version 10.0.19.
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>= 9.1.0, < 10.0.19CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify GLPI versionCheck the installed GLPI version by accessing the version file (typically /inc/commonitilobject.class.php or the version constant defined in the codebase) or by checking the footer of the GLPI web interface. Run: grep -r 'VERSION' /path/to/glpi/inc/ or view the general setup page.Affected if The installed version is 9.1.0 through 10.0.18 (any version >= 9.1.0 and < 10.0.19)
-
Confirm planning feature is accessibleNavigate to the GLPI planning module (typically accessed via /front/planning.php or the Planning link in the main menu) without logging in to determine if the endpoint is reachable without authentication.Affected if The planning page loads or returns a valid response without requiring login credentials
-
Check external/unauthenticated access exposureDetermine if the GLPI instance is accessible from the internet or untrusted networks by testing access to the planning endpoint from an unauthenticated browser session or using curl: curl -I http://your-glpi-host/front/planning.phpAffected if The planning feature responds to unauthenticated requests from external/unntrusted network locations
You are affected if your GLPI version is 9.1.0 through 10.0.18 and the planning feature is accessible to unauthenticated users.
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.19
Upgrade GLPI to version 10.0.19 or later to remediate this vulnerability. As a defense-in-depth measure, consider implementing email filtering and user training to mitigate phishing risks.
GLPI 10.0.19
- 1. Back up the current GLPI database and files before proceeding with the upgrade
- 2. Download GLPI version 10.0.19 from the official GitHub repository (github.com/glpi-project/glpi)
- 3. Follow the standard GLPI upgrade procedure: disable plugins, replace files with new version, run the install/update script
- 4. Re-enable plugins after confirming the upgrade is successful
- 5. Verify the planning feature no longer allows unauthenticated malicious links
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52897 — 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-2025-52897 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