CVE-2009-2266
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 · uneditedOXID eShop 4.x before 4.1.4-21266, 3.x, and 2.x allows remote attackers to obtain sensitive information (session details and order history of other users) via a crafted 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 confidenceOXID eShop versions 4.x before 4.1.4-21266, 3.x, and 2.x contain a cookie handling vulnerability that allows remote attackers to bypass proper session validation. By crafting malicious cookies, attackers can impersonate other users and access their sensitive session data including order history.
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<= 2.7.0.3<= 3.0.4.1= 4.0.0.0_13895= 4.0.0.0_13934= 4.0.0.0_14260= 4.0.0.1_14455= 4.0.0.2_14842= 4.0.0.2_14967= 4.0.1.0_15990= 4.1.0-17976= 4.1.1-18442= 4.1.2-18998CVSS 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.
-
Locate OXID eShop installation directoryIdentify the web root where OXID eShop is installed. Check directories like /var/www/html/, /www/, or the document root of the web server for OXID-specific files such as index.php, config.inc.php, or the oxseo.php core file.Affected if OXID eShop files are present in the web root
-
Identify installed OXID eShop versionOpen the file /core/oxversion.php in a text editor or web browser. This file contains a constant defining the exact version number. Alternatively, check the CHANGELOG.txt file in the root directory which lists version information.Affected if The version number matches any of these vulnerable builds: 2.7.0.3 or lower; 3.0.4.1 or lower; 4.0.0.0_13895; 4.0.0.0_13934; 4.0.0.0_14260; 4.0.0.1_14455; 4.0.0.2_14842; 4.0.0.2_14967; 4.1.0-17976; 4.1.1-18442; 4.1.2-18998
-
Confirm session cookie handling is activeVerify the application is using cookie-based sessions by checking the config.inc.php file for session handling settings. Look for parameters related to cookie handling in the session configuration section.Affected if Cookie-based sessions are enabled and the version is in the affected list above
If the installed version is any 2.x, 3.x, or 4.x build before 4.1.4-21266, the cookie handling vulnerability exists and session hijacking is possible.
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 to OXID eShop 4.1.4-21266 or later. Additionally, review and regenerate session identifiers and validate cookie contents server-side to prevent session hijacking or cross-user data access.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-2266 — 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-2009-2266 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