CVE-2012-4002
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 · uneditedCross-site request forgery (CSRF) vulnerability in GLPI-PROJECT GLPI before 0.83.3 allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.
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 confidenceCross-site request forgery (CSRF) vulnerability in GLPI before version 0.83.3 allows remote attackers to hijack the authentication of unspecified victims by tricking authenticated users into unknowingly submitting malicious requests.
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.83.2= 0.5= 0.6= 0.20= 0.21= 0.30= 0.31= 0.40= 0.41= 0.42= 0.51= 0.51aCVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 number in the GLPI application footer, on the Home > Assistance > About page, or in the version.php file within the inc/ directoryAffected if The displayed version is 0.83.2 or earlier, or matches any of these specific versions: 0.5, 0.6, 0.20, 0.21, 0.30, 0.31, 0.40, 0.41, 0.42, 0.51, or 0.51a
-
Verify GLPI is accessible over networkConfirm the GLPI web interface is reachable and accepting connectionsAffected if GLPI is running and accessible to users or attackers on the network
-
Confirm authenticated sessions are possibleCheck whether user authentication is enabled and users can log in to GLPIAffected if User login functionality is active and authenticated sessions can be established
-
Inspect form handling for CSRF protectionExamine the HTML source of state-changing forms (e.g., user management, settings, ticket creation) for the presence of anti-CSRF tokens or token validation logic in the backend codeAffected if Forms lack anti-CSRF token fields and the application does not validate Origin/Referer headers on POST requests
A GLPI installation is affected if it runs any version listed as vulnerable (0.83.2 or earlier, or any of the specific versions 0.5 through 0.51a) AND allows authenticated user sessions, since the flaw allows malicious requests to be forged by tricking logged-in users.
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 to GLPI version 0.83.3 or later. As an interim measure, implement anti-CSRF tokens on all state-changing forms and validate the Origin/Referer headers on POST requests.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4002 — 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-2012-4002 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