CVE-2010-5084
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 · uneditedThe cross-site request forgery (CSRF) protection mechanism in e107 before 0.7.23 uses a predictable random token based on the creation date of the administrator account, which allows remote attackers to hijack the authentication of administrators for requests that add new users via e107_admin/users.php.
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 confidencee107 before version 0.7.23 uses a CSRF token generation mechanism that derives tokens from the administrator account's creation date. Because this timestamp is predictable rather than cryptographically random, an attacker can forge valid CSRF tokens and hijack authenticated administrator sessions to create unauthorized user accounts via e107_admin/users.php.
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.7.22= 0.6_10= 0.6_11= 0.6_12= 0.6_13= 0.6_14= 0.6_15= 0.6_15a= 0.7= 0.7.0= 0.7.1= 0.7.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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/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.
-
Check installed e107 versionLog into the e107 admin panel and look for the version number in the admin dashboard footer, or check the file e107_handlers/version.php for the version constantAffected if The version is 0.7.22 or earlier, or matches any of these: 0.6_10, 0.6_11, 0.6_12, 0.6_13, 0.6_14, 0.6_15, 0.6_15a, 0.7, 0.7.0, 0.7.1, 0.7.2
-
Locate the CSRF token generation codeExamine the file e107_handlers/secure_img_render.php or the file containing the getCSRFToken function, looking for token generation logicAffected if The token generation code uses a method like md5(user_create_timestamp) or derives the token from the admin account creation date rather than using a cryptographically random value
-
Identify the admin account creation timestamp sourceCheck the e107_users table in the database for the user_join or user_created field for the admin account (usually user_id = 1), or view the admin account details in the admin users pageAffected if The admin account creation timestamp is stored as a Unix timestamp and is used as input to the CSRF token generation
-
Verify token predictabilityGenerate a CSRF token, then manually compute what the token would be using the formula: md5(admin_user_id + user_join_timestamp) or similar derivation, and compare it to the actual tokenAffected if The generated token matches a token computed from the admin account creation timestamp, confirming the vulnerable predictable algorithm is in use
You are affected if your e107 version is 0.7.22 or earlier and the CSRF token generation derives tokens from the administrator account creation timestamp rather than using cryptographic randomness.
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 e107 to version 0.7.23 or later, which implements proper cryptographic randomness for CSRF token generation. Until upgraded, monitor admin activity logs for unauthorized user creation attempts.
- Consultation2.0 h
- Implementation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5084 — 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-2010-5084 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