dbcve.org
MozilocmsApplication · Mozilo

CVE-2008-6128

MEDIUM · 6.8 CVSS v2.0 Published 2009-02-13
Fix available
A fix is available. Upgrade to after 1.10.2 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 moziloCMS 1.10.2 and earlier 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

moziloCMS 1.10.2 and earlier contains a session fixation vulnerability where remote attackers can hijack web sessions by setting the PHPSESSID parameter. This allows attackers to pre-establish a session ID that victims then use, enabling session hijacking.

MitigationRegenerate session IDs upon user authentication and reject session IDs provided via user-supplied input such as the PHPSESSID parameter to prevent session fixation attacks.

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
MozilocmsApplication
Affected:<= 1.10.2= 1.0= 1.1= 1.1.1= 1.2= 1.3= 1.3.1= 1.4= 1.5= 1.6= 1.6.1= 1.6.2

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 if moziloCMS is installed
    Look for the presence of moziloCMS directories such as 'cms', 'editor', or 'syntax' in the web root, or check for the existence of typical moziloCMS files like 'index.php', 'admin.php', or 'config.php'.
    Affected if moziloCMS is present on the server in the web-accessible directory.
  2. Determine the installed moziloCMS version
    Open the main index.php file in a text editor or via command line and look for a version string. In moziloCMS, the version is typically defined near the top of index.php or in a separate version include file.
    Affected if The version number found is 1.10.2 or earlier, or matches one of: 1.0, 1.1, 1.1.1, 1.2, 1.3, 1.3.1, 1.4, 1.5, 1.6, 1.6.1, 1.6.2.
  3. Check if PHP session.use_only_cookies is disabled
    Inspect the PHP configuration file (php.ini) or check the current PHP settings using phpinfo(). Look for the session.use_only_cookies directive.
    Affected if session.use_only_cookies is set to 0 or Off, allowing session IDs to be passed via URL parameters or the PHPSESSID parameter.
  4. Test for session fixation vulnerability
    Make an HTTP request to the moziloCMS site setting a custom PHPSESSID value (e.g., PHPSESSID=test123456). Then visit another page on the same site and verify if the same PHPSESSID value persists in cookies or is accepted by the application.
    Affected if The application accepts and maintains the user-supplied PHPSESSID value across requests without regenerating it.
  5. Verify session ID regeneration behavior
    Examine the source code for session handling, particularly in login-related files. Search for calls to session_regenerate_id() or session_destroy() after user authentication occurs.
    Affected if The application does not regenerate session IDs upon login or authentication, allowing an attacker who sets a PHPSESSID value to maintain that session after the victim authenticates.

A user is affected if moziloCMS version 1.10.2 or earlier is installed and the application accepts user-supplied PHPSESSID values without regenerating session IDs on authentication.

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.10.2
Interim mitigation

Regenerate session IDs upon user authentication and reject session IDs provided via user-supplied input such as the PHPSESSID parameter to prevent session fixation attacks.

Fix this in Mozilocms 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-6128 — 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-6128 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