CVE-2019-17062
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 · uneditedAn issue was discovered in OXID eShop 6.x before 6.0.6 and 6.1.x before 6.1.5, OXID eShop Enterprise Edition Version 5.2.x-5.3.x, OXID eShop Professional Edition Version 4.9.x-4.10.x and OXID eShop Community Edition Version: 4.9.x-4.10.x. By using a specially crafted URL, users with administrative rights could unintentionally grant unauthorized users access to the admin panel via session fixation.
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 contains a session fixation vulnerability where attackers can use a specially crafted URL to pre-establish a session ID that will be inherited by an authenticated admin user. Once the admin user logs in with this fixed session ID, the attacker can hijack the admin session and gain unauthorized access to the admin panel.
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.9.0, <= 4.10.0>= 5.2.0, <= 5.3.0>= 6.0.0, < 6.0.6>= 6.1.0, < 6.1.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 versionCheck the version file (e.g., /source/OxidEsales/Eshop/release.json or /source/Application/Model/Shop.php) or log into the admin panel and check the 'System' > 'Info' section for the version numberAffected if The installed version falls within 4.9.0-4.10.0, 5.2.0-5.3.0, 6.0.0-6.0.5, or 6.1.0-6.1.4
-
Verify session ID regeneration on loginExamine the authentication source code (typically in /source/Application/Controller/Admin/LoginController.php or similar) and look for session_regenerate_id() or session_create_id() calls within the login handling functionAffected if The login handler does NOT call session_regenerate_id() or equivalent after successful authentication, meaning session IDs are not regenerated upon admin login
-
Check session invalidation on loginSearch the authentication and session handling code for session_unset() or session_destroy() calls that should invalidate the previous session ID after successful loginAffected if Previous session IDs are NOT invalidated after admin authentication, allowing a fixed session ID to persist after login
-
Inspect session cookie configurationCheck the session configuration file (usually config.inc.php or php.ini) for session.cookie_httponly, session.cookie_secure, and session.cookie_samesite settingsAffected if Session cookies lack HttpOnly, Secure, or SameSite attributes, leaving them vulnerable to being accessed via JavaScript or transmitted over insecure connections
You are affected if your OXID eShop version is within the affected ranges AND the login process does not regenerate/invalidate session IDs upon admin authentication.
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 data6.0.66.1.5
Regenerate session IDs upon user authentication (login) and implement secure session cookie attributes (HttpOnly, Secure, SameSite). Additionally, invalidate previous session IDs on login to prevent session fixation attacks.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17062 — 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-2019-17062 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