CVE-2008-2558
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 · uneditedCRE Loaded 6.2.13.1 and earlier does not set the "Secure" attribute for cookies that are sent over HTTPS, which might allow remote attackers to sniff the cookies if they are sent over HTTP.
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 confidenceCRE Loaded 6.2.13.1 and earlier fails to set the 'Secure' flag on session cookies, meaning cookies can be transmitted over unencrypted HTTP connections where they may be intercepted by network sniffers.
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<= 6.2.13.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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 the installed CRE Loaded versionLocate and inspect version identification files in the web root (commonly version.php, version_info.php, or includes/application_top.php) and look for version strings like '6.2.13.1' or earlierAffected if The installed version is 6.2.13.1 or any earlier version of CRE Loaded
-
Verify if session cookies are missing the Secure flagCapture HTTP traffic or inspect browser developer tools (Application/Storage tab) to view cookies set by the application during a login or session establishmentAffected if Session cookies (typically osCsid or similar) do not have the 'Secure' attribute checked in the cookie details
-
Check cookie generation code in session handlerExamine the session management files (such as includes/sessions.php or includes/functions/sessions.php) for the session_set_cookie_params or setcookie function callsAffected if The code does not include the 'Secure' parameter or passes it as false/null when setting session cookies
-
Confirm the application accepts HTTP connectionsAttempt to access the storefront over HTTP (non-HTTPS) on the standard HTTP port (typically 80)Affected if The application serves pages over unencrypted HTTP, allowing session cookies to be transmitted in cleartext
You are affected if you run CRE Loaded version 6.2.13.1 or earlier AND the application accepts HTTP connections AND session cookies lack the Secure flag, meaning they could be intercepted by network sniffers.
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 dataConfigure the application to set the 'Secure' attribute on all cookies, ensuring they are only transmitted over encrypted HTTPS connections.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-2558 — 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-2558 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