CVE-2010-1136
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 Standard Remember method in TikiWiki CMS/Groupware 3.x before 3.5 allows remote attackers to bypass access restrictions related to "persistent login," probably due to the generation of predictable cookies based on the IP address and User agent in userslib.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 confidenceThe Standard Remember method in TikiWiki CMS/Groupware 3.x before 3.5 uses predictable values (IP address and User agent) to generate authentication cookies in userslib.php. This allows remote attackers to craft valid persistent login cookies and bypass authentication, gaining unauthorized access to user accounts.
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= 3.0= 3.1= 3.2= 3.3= 3.4CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/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 TikiWiki versionCheck the version file or admin panel for the exact TikiWiki CMS/Groupware version numberAffected if The installed version is 3.0, 3.1, 3.2, 3.3, or 3.4 (versions before 3.5)
-
Locate userslib.php authentication codeFind the userslib.php file in the TikiWiki installation directory and examine the remember me cookie generation functionAffected if The file contains cookie generation logic using IP address and User agent string concatenation without cryptographic randomization
-
Verify remember me feature is enabledCheck the TikiWiki authentication settings (tiki-login.php or admin panel) for the 'remember me' or 'Standard Remember' login optionAffected if The Standard Remember method is active and cookies are being generated for persistent sessions
-
Examine cookie structureInspect a remember me cookie in the browser or capture one via network logging; check if it contains predictable values like IP address or User agentAffected if The cookie value can be reconstructed using only client IP and User agent information
A user is affected if they are running TikiWiki versions 3.0 through 3.4 with the Standard Remember feature enabled, as the authentication cookie generation relies on predictable IP/UA values rather than 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 dataReplace the predictable cookie generation algorithm with cryptographically secure random values (e.g., using random_bytes() or similar) and implement proper session token validation rather than relying on IP/UA combinations.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1136 — 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-1136 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