CVE-2015-6926
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 · uneditedThe OpenID Single Sign-On authentication functionality in OXID eShop before 4.5.0 allows remote attackers to impersonate users via the email address in a crafted authentication token.
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 confidenceThe OpenID Single Sign-On authentication in OXID eShop before version 4.5.0 contains a flaw allowing remote attackers to craft authentication tokens containing arbitrary email addresses, enabling user impersonation. This bypasses the authentication mechanism by exploiting how the OpenID SSO processes email claims in tokens.
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>= 4.0.1.0, <= 4.4.8CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 OXID eShop installation versionLocate the version file or bootstrap file in the OXID installation directory and read the reported version numberAffected if The installed version falls within the range 4.0.1.0 to 4.4.8 (inclusive)
-
Verify OpenID SSO module is installedCheck the modules directory for OpenID-related files or check the OXID module configuration for OpenID SSO componentsAffected if The OpenID SSO module is present in the installation
-
Confirm OpenID SSO feature is enabledInspect the OXID configuration files or admin panel settings to determine if the OpenID Single Sign-On authentication method is activeAffected if OpenID SSO is enabled as an authentication method in the system configuration
-
Review OpenID authentication configurationExamine the OpenID configuration files or database settings that handle email claim processing in authentication tokensAffected if The OpenID configuration allows external email claims to be accepted without proper validation in the token processing logic
A system is affected if it runs OXID eShop versions 4.0.1.0 through 4.4.8 with the OpenID SSO module installed and enabled, allowing unvalidated email claims in authentication tokens to impersonate users.
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 OXID eShop to version 4.5.0 or later to obtain the patched OpenID SSO implementation, or disable the OpenID SSO feature if upgrading is not feasible.
- 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-2015-6926 — 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-2015-6926 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