CVE-2007-1953
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 · uneditedSession fixation vulnerability in onelook courts on-line allows remote attackers to hijack web sessions by setting a PHPSESSID cookie.
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 confidenceThis is a session fixation vulnerability in a PHP-based web application where attackers can set the PHPSESSID cookie to a predetermined value before the victim authenticates. Once the victim logs in using that attacker-controlled session ID, the attacker can hijack the authenticated session by using the same session identifier.
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 dataall versionsCVSS 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 Onelook Courts Online installationLocate the web application files on the server. Search for files containing 'Onelook Courts Online', 'onelook', or 'courts' in the web root directory.Affected if The application is present on the server and handles sensitive court-related operations.
-
Verify PHP session handling is in useReview the application source code for calls to session_start() or references to $_SESSION. Check if the application sets or reads the PHPSESSID cookie.Affected if The application uses PHP sessions for maintaining user state, indicated by session_start() calls or PHPSESSID cookie handling.
-
Check for client-supplied session ID acceptanceAnalyze the session initialization code to determine if the application accepts session IDs provided by the client via cookies or URL parameters without validation. Look for $_COOKIE['PHPSESSID'] or $_GET['PHPSESSID'] being passed directly to session_id().Affected if The application accepts and uses session IDs that originate from client requests without server-side validation or rejection.
-
Examine authentication code for session regenerationReview the login/authentication logic to determine whether session_regenerate_id() is called after successful authentication. Search the authentication handlers for this function.Affected if The login process does NOT call session_regenerate_id(true) after successful authentication, allowing session fixation to persist.
A user is affected if Onelook Courts Online is installed, uses PHP sessions with the PHPSESSID cookie, accepts client-supplied session IDs without validation, and fails to regenerate session IDs after authentication.
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 dataRegenerate session IDs immediately after successful authentication using session_regenerate_id(true)) and implement server-side session ID validation to reject session IDs provided by clients, ensuring only server-generated IDs are accepted.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1953 — 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-2007-1953 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