CVE-2019-13026
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 6.0.x before 6.0.5 and 6.1.x before 6.1.4 allows SQL Injection via a crafted URL, leading to full access by an attacker. This includes all shopping cart options, customer data, and the database. No interaction between the attacker and the victim is necessary.
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 6.0.x before 6.0.5 and 6.1.x before 6.1.4 contains a SQL Injection vulnerability in URL parameter handling that allows unauthenticated attackers to inject arbitrary SQL queries, leading to full database compromise including customer data and shopping cart information.
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.0.0, < 6.0.5>= 6.1.0, < 6.1.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 installed versionLocate the version file or check the admin panel for the current OXID eShop version number. Common locations include a version.php file in the source directory or the 'About' section in the admin backend.Affected if The version number matches the affected ranges: 6.0.0 through 6.0.4, or 6.1.0 through 6.1.3
-
Compare version to CVE-affected rangesCompare your installed version against the vulnerable ranges: 6.0.x where x < 5, and 6.1.x where x < 4.Affected if Your installed version is 6.0.0 to 6.0.4, or 6.1.0 to 6.1.3
-
Verify web-facing accessibilityConfirm that the OXID eShop storefront or admin interface is accessible over HTTP/HTTPS.Affected if The shop is publicly accessible and the version falls within the affected ranges listed above
You are affected if your OXID eShop installation version is 6.0.0 through 6.0.4 or 6.1.0 through 6.1.3 and the application is accessible over the web, since the SQL injection flaw is in URL parameter handling and can be exploited by unauthenticated attackers.
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.
dbcve · scoped6.0.56.1.4
Update OXID eShop to version 6.0.5 or 6.1.4 or later to patch the SQL Injection vulnerability.
OXID eShop 6.0.5+ or 6.1.4+ (depending on your current branch)
- 1. Backup the entire OXID eShop installation including the database before proceeding with any upgrade
- 2. Download OXID eShop version 6.0.5 or later (for 6.0.x installations) or version 6.1.4 or later (for 6.1.x installations) from the official OXID eShop repository
- 3. Replace the existing shop files with the new version files, preserving custom configurations and theme files
- 4. Run the shop's update process/database migration to ensure all schema changes are applied
- 5. Clear all cache directories (tmp/ and out/cache/) to ensure new code is used
- 6. Verify the installation by accessing the admin panel and testing basic functionality
- 7. Test that the SQL injection vulnerability is remediated by attempting the previously vulnerable URL pattern
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13026 — 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-13026 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