CVE-2008-4689
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 · uneditedMantis before 1.1.3 does not unset the session cookie during logout, which makes it easier for remote attackers to hijack sessions.
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 confidenceMantisBT before version 1.1.3 fails to properly destroy or unset the session cookie when a user logs out. This leaves the session token valid on the server, allowing an attacker who obtains the session cookie (via network sniffing, XSS, or malware) to hijack the user's authenticated session even after legitimate logout.
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<= 1.1.2= 0.19.3= 0.19.4= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.1.1CVSS 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.
-
Locate MantisBT installation directoryIdentify the web server document root or directory where MantisBT is installed. Look for the main file (index.php) or the config file (config_inc.php).Affected if Unable to locate MantisBT installation - not applicable for this check.
-
Determine installed MantisBT versionOpen the file 'core.php' or 'version.php' in the MantisBT root directory and look for a version constant (such as MANTIS_VERSION or $g_version). Alternatively, log into the MantisBT web interface and check the footer or 'My Account' > 'Preferences' page for the version number.Affected if Version number cannot be determined - further investigation needed.
-
Compare version against affected rangesReview the version found in step 2. Affected versions are: all releases ≤ 1.1.2, and specifically versions 0.19.3, 0.19.4, 1.0.1 through 1.0.8, and 1.1.1. Compare your installed version to this list.Affected if Installed version is 1.1.2 or earlier, or matches any of the specific affected versions listed (0.19.3, 0.19.4, 1.0.x series, or 1.1.1).
-
Verify session handling on logout (optional)If source code access is available, examine the logout function in 'core/session_api.php' or the file handling logout actions. Look for whether session_destroy() or session_unset() is properly called during the logout process.Affected if The logout code does not call session_destroy() or properly invalidate the session cookie - indicating the vulnerability is present.
You are affected if your MantisBT installation runs version 1.1.2 or earlier, or matches any of the specific vulnerable versions (0.19.3, 0.19.4, 1.0.1-1.0.8, 1.1.1), regardless of configuration settings.
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 MantisBT to version 1.1.3 or later, which implements proper session cookie destruction on logout. Consider rotating active sessions and invalidating existing sessions after the upgrade.
- Consultation1.0 h
- Implementation3.0 h
- Testing2.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,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-4689 — 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-2008-4689 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