CVE-2025-24801
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. An authenticated user can upload and force the execution of *.php files located on the GLPI server. This vulnerability is fixed in 10.0.18.
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 confidenceAuthenticated users can upload malicious PHP files to the GLPI server and force their execution, leading to remote code execution. This is a critical file upload vulnerability in GLPI's file handling that allows attackers with valid credentials to achieve RCE.
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.85, < 10.0.18CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 versionLocate the version.php file in your GLPI root directory (typically at /glpi/version.php or similar path) and read the $CFG_GLPI['version'] value. Alternatively, check the bottom of the GLPI login page or access Setup > General > System Information in the web interface.Affected if The installed version is 0.85 or higher but lower than 10.0.18 (e.g., 9.5.x, 10.0.10, 10.0.17)
-
Verify authenticated file upload is enabledLog into GLPI with a standard user account and navigate to the profile or ticket creation area where attachments can be added. Attempt to verify whether the file upload feature is accessible to authenticated (non-admin) users.Affected if Authenticated users have access to the file upload feature and can attach files to tickets, documents, or profiles
-
Check web server PHP execution in upload directoriesExamine your web server configuration (Apache/nginx) for handlers that allow PHP execution in the GLPI files directory (usually /glpi/files/ or /glpi/_uploads/). Look for any AddType or location directives that permit PHP execution in these paths.Affected if The web server is configured to execute PHP files located in GLPI's upload directories
-
Inspect upload directories for suspicious PHP filesUse a file listing command (such as find or ls) to scan GLPI's upload directories (typically /glpi/files/, /glpi/_uploads/, or /glpi/uploads/) for any .php files that were not intentionally uploaded by administrators.Affected if Any .php files exist in the upload directories, especially those with suspicious names or recent modification dates
-
Review access logs for file upload activityExamine your web server access logs (access.log or error.log) for POST requests to GLPI's file upload endpoints (often /glpi/ajax/fileupload.php or similar) that include .php file extensions in the upload parameters.Affected if Logs show authenticated users uploading files with .php extensions to GLPI
You are affected if your GLPI version is 10.0.17 or lower (0.85 through 10.0.17), authenticated users can upload files, and your web server allows PHP execution in upload directories.
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.18
Upgrade GLPI to version 10.0.18 or later to patch the file upload vulnerability. Until patched, restrict or monitor file upload capabilities and review access controls for privileged users.
GLPI 10.0.18
- Create a complete backup of the GLPI database and files
- Download GLPI version 10.0.18 from the official GLPI website or GitHub repository
- Follow the standard GLPI upgrade procedure: unzip the new version, copy the files to the web server document root, run the upgrade script or visit the GLPI URL to trigger the database upgrade
- Verify the upgrade was successful by logging in and checking the GLPI version
- Test critical functionality to ensure the upgrade did not break existing workflows
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24801 — 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-24801 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