CVE-2015-7684
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 · uneditedUnrestricted file upload in GLPI before 0.85.3 allows remote authenticated users to execute arbitrary code by adding a file with an executable extension as an attachment to a new ticket, then accessing it via a direct request to the file in files/_tmp/.
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 confidenceGLPI before version 0.85.3 contains an unrestricted file upload vulnerability that allows authenticated users to attach files with executable extensions (such as .php) to tickets. Since uploaded files are stored in the publicly accessible files/_tmp/ directory, attackers can directly request the uploaded file to achieve arbitrary code execution on the server.
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.2CVSS 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
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/C:C/I:C/A:C
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.
-
Determine GLPI versionCheck the version.php file in the GLPI root directory, or access the login page footer which typically displays the version numberAffected if The installed version is 0.85.2 or lower
-
Locate the upload tmp directoryCheck for the existence of the files/_tmp/ or _tmp/ directory within the GLPI web rootAffected if The directory exists and is web-accessible
-
Verify web server serves files/_tmp/ directoryAttempt to access a known file in files/_tmp/ via HTTP request to see if the web server serves files from this locationAffected if The directory is directly accessible via HTTP without authentication
-
Check if document upload is permitted for ticketsLog in as a regular user and attempt to attach a file with a .php extension to a ticket, or inspect the document types configuration in the GLPI administration panelAffected if Users can attach files with executable extensions like .php to tickets
A user is affected if running GLPI version 0.85.2 or lower and the files/_tmp/ directory is web-accessible with executable file uploads enabled for tickets.
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 · scopedUpgrade to GLPI version 0.85.3 or later, which implements proper file extension validation and restricts executable file types from being uploaded as attachments. Additionally, ensure the upload directory is not directly executable via the web server.
0.85.3
- Backup your current GLPI installation and database before proceeding
- Download GLPI version 0.85.3 from the official GLPI project repository or website
- Extract the new version and replace the existing GLPI files on your server
- Ensure proper file permissions are maintained after the upgrade
- Access the GLPI web interface to complete any database upgrades if prompted
- Verify the upgrade was successful by checking the GLPI version in the administration panel
- Confirm that the files/_tmp/ directory now has proper restrictions on executable file types
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7684 — 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-2015-7684 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