dbcve.org
ImpresscmsApplication

CVE-2008-5964

MEDIUM · 6.8 CVSS v2.0 Published 2009-01-23
Fix available
A fix is available. Upgrade to after 1.0.3 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Session fixation vulnerability in Social ImpressCMS before 1.1.1 RC1 allows remote attackers to hijack web sessions by setting the PHPSESSID parameter.

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 confidence

Session fixation vulnerability in ImpressCMS prior to 1.1.1 RC1 allows remote attackers to hijack web sessions by manipulating the PHPSESSID parameter. The application accepts attacker-controlled session IDs, enabling session prediction and session hijacking after victim authentication.

MitigationRegenerate session IDs upon user authentication using session_regenerate_id() and validate that session IDs are not accepted from user-supplied GET/POST parameters; upgrade to version 1.1.1 RC1 or later.

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
ImpresscmsApplication
Affected:<= 1.0.3= 1.0= 1.0.1= 1.0.2= 1.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ImpressCMS version
    Locate the version file or header in your ImpressCMS installation (typically in version.php or similar version documentation file) and note the exact version number
    Affected if Version is 1.0, 1.0.1, 1.0.2, 1.0.3, or 1.1 (versions prior to 1.1.1 RC1)
  2. Verify session ID handling from user input
    Review the application code that handles the PHPSESSID parameter. Search for code that accepts session IDs from GET or POST requests without validation
    Affected if The application accepts and uses session IDs provided directly in PHPSESSID parameters from user requests
  3. Check for session regeneration on authentication
    Search the login and authentication code for calls to session_regenerate_id() function that should occur after successful user authentication
    Affected if No session_regenerate_id() call is found after user login, meaning session IDs are not regenerated upon authentication

You are affected if your ImpressCMS version is 1.1 or earlier AND the application accepts user-supplied session IDs without regenerating them upon login.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0.3
Interim mitigation

Regenerate session IDs upon user authentication using session_regenerate_id() and validate that session IDs are not accepted from user-supplied GET/POST parameters; upgrade to version 1.1.1 RC1 or later.

Fix this in Impresscms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-5964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-5964 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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