CVE-2014-5032
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 before 0.84.7 does not properly restrict access to cost information, which allows remote attackers to obtain sensitive information via the cost criteria in the search bar.
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 before version 0.84.7 contains an access control weakness in its search functionality. The application fails to properly restrict access to cost information, allowing remote attackers to retrieve sensitive financial data by using cost criteria in the search bar without proper authorization.
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.84.6CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Identify installed GLPI versionLocate the version file or configuration in the GLPI installation directory. Common locations include a version.php file, the config table in the database, or the footer of the web interface. Compare the version number to the affected range (0.84.6 and below).Affected if The installed GLPI version is 0.84.6 or earlier.
-
Verify search functionality is accessibleConfirm that the GLPI web application is operational and the search feature is available to users. Access the main search bar or search module through the web interface.Affected if The search functionality is enabled and accessible to the user.
-
Check for cost-related search criteriaExamine the search criteria options available in the search interface. Look for fields related to cost, price, budget, or financial information that can be used as filter parameters.Affected if Cost criteria fields are available in the search options without additional access controls.
-
Test unauthorized cost data retrievalUse the search functionality with cost-related criteria to query for items. Attempt to retrieve financial data (such as device costs, contract prices, or budget information) without proper administrative or role-based authorization.Affected if Sensitive cost information is returned in search results without proper authorization checks.
A user is affected if GLPI version 0.84.6 or earlier is installed AND the search functionality with cost criteria is accessible, allowing unauthorized retrieval of financial data.
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.
From vendor dataUpgrade GLPI to version 0.84.7 or later, which contains the proper access restrictions for cost information. Alternatively, review and implement role-based access controls on the search functionality to enforce proper authorization before displaying cost-sensitive data.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5032 — 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-2014-5032 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