CVE-2026-23489
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 · uneditedFields is a GLPI plugin that allows users to add custom fields on GLPI items forms. Prior to version 1.23.3, it is possible to execute arbitrary PHP code from users that are allowed to create dropdowns. This issue has been patched in version 1.23.3.
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 confidenceThe Fields GLPI plugin versions prior to 1.23.3 contain a code injection vulnerability allowing authenticated users with dropdown creation privileges to execute arbitrary PHP code on the server. This stems from improper sanitization of dropdown configuration input, enabling attackers to inject and execute malicious PHP payloads.
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< 1.23.3CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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.
-
Confirm Fields plugin is installedNavigate to GLPI Administration > Plugins or check the plugins directory to verify the Fields plugin is present in your installationAffected if The Fields plugin by Teclib is installed and active in GLPI
-
Identify Fields plugin versionIn GLPI, go to Administration > Plugins > Fields plugin and locate the version number displayedAffected if The installed version is prior to 1.23.3 (for example, 1.23.2, 1.22.0, etc.)
-
Review dropdown creation permissionsNavigate to GLPI Administration > Profiles > [Selected Profile] > Assistance or specific permission section to check which users or profiles have dropdown creation or management privilegesAffected if Any user profile has dropdown creation or management permissions enabled, especially for non-administrator accounts
-
Inspect dropdown configurations for injected codeGo to Setup > Dropdowns in GLPI and examine existing dropdown configurations, checking the source code or configuration values for suspicious PHP code patterns (such as <?php, system, exec, shell_exec, or base64_decode)Affected if Any dropdown configuration contains PHP code or suspicious payloads that were not intentionally configured by administrators
You are affected if the Fields plugin version is below 1.23.3 AND any user account with dropdown creation privileges exists in your GLPI instance, or if malicious PHP code is found in dropdown configurations.
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 · scoped1.23.3
Upgrade the Fields GLPI plugin to version 1.23.3 or later immediately. Review and audit user permissions for dropdown creation capabilities, and consider restricting this permission to only trusted administrators until the patch is applied.
Fields plugin version 1.23.3
- 1. Back up the current Fields plugin directory and the GLPI database before proceeding with any changes
- 2. Download Fields plugin version 1.23.3 from the official GLPI plugin repository or the project's GitHub releases page
- 3. Navigate to the GLPI plugins directory (typically /glpi/plugins/)
- 4. Remove or rename the existing 'fields' plugin folder
- 5. Extract the new Fields plugin version 1.23.3 into the plugins directory
- 6. Ensure the folder is named 'fields'
- 7. Log into GLPI as an administrator
- 8. Navigate to Setup > Plugins
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23489 — 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-2026-23489 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