dbcve.org
GlpiApplication · Glpi Project

CVE-2023-42802

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-02
Fix available
A fix is available. Upgrade to 10.0.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
GLPI is a free asset and IT management software package. Starting in version 10.0.7 and prior to version 10.0.10, an unverified object instantiation allows one to upload malicious PHP files to unwanted directories. Depending on web server configuration and available system libraries, malicious PHP files can then be executed through a web server request. Version 10.0.10 fixes this issue. As a workaround, remove write access on `/ajax` and `/front` files to the web server.

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 confidence

GLPI versions 10.0.7 through 10.0.9 suffer from an unverified object instantiation vulnerability that enables attackers to upload malicious PHP files to arbitrary directories. When the web server is configured to execute PHP in these locations, this leads to remote code execution.

MitigationUpgrade to GLPI version 10.0.10 or later. As a workaround, remove write access on `/ajax` and `/front` directories to the web server user.

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
GlpiApplication
Affected:>= 10.0.7, < 10.0.10

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify GLPI version
    Locate the version file typically at src/DbUtils.php or src/Version.php, or check the admin dashboard under Setup > General > System for the version number
    Affected if the installed version is 10.0.7, 10.0.8, or 10.0.9 (greater than or equal to 10.0.7 and less than 10.0.10)
  2. Verify /ajax directory permissions
    Check if the web server user has write access to the /ajax directory by reviewing file system permissions or using commands like ls -la on the ajax folder at the web root
    Affected if the web server user can write to the /ajax directory (directory is writable by the web server process)
  3. Verify /front directory permissions
    Check if the web server user has write access to the /front directory by reviewing file system permissions or using commands like ls -la on the front folder at the web root
    Affected if the web server user can write to the /front directory (directory is writable by the web server process)
  4. Check PHP execution configuration in /ajax and /front
    Examine the .htaccess file in /ajax and /front directories, or review the Apache/Nginx vhost configuration to determine if PHP scripts in these directories can be executed
    Affected if PHP execution is permitted in the /ajax or /front directories (no restriction configured)

You are affected if GLPI version is 10.0.7 through 10.0.9 AND the web server has write access to /ajax or /front directories with PHP execution enabled in those locations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.10 or later
Fixed in 10.0.10
Interim mitigation

Upgrade to GLPI version 10.0.10 or later. As a workaround, remove write access on `/ajax` and `/front` directories to the web server user.

Recommended fix High confidence

GLPI 10.0.10

  1. 1. Create a complete backup of the GLPI database and the existing GLPI installation directory
  2. 2. Download GLPI version 10.0.10 from the official GLPI website (glpi-project.org)
  3. 3. Extract the downloaded archive to a temporary location
  4. 4. Replace the existing GLPI files with the new version, preserving the config/local_define.php file and any custom plugins
  5. 5. Verify the file ownership and permissions are correct for the web server user
  6. 6. Run the upgrade by accessing GLPI through a web browser or using the command line tool if available
  7. 7. Verify the application loads correctly and all functionalities work as expected
  8. 8. Confirm version 10.0.10 is now running in the GLPI General Setup > General > System information
Caveat Minor upgrades within the 10.x line typically have minimal breaking changes; review the release notes for any deprecations or configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glpi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-42802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-42802 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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