dbcve.org
Ec CubeApplication · Lockon

CVE-2014-0808

CRITICAL · 9.1 CVSS v3.1 Published 2014-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Authorization bypass through user-controlled key issue exists in EC-CUBE 2.11.0 through 2.12.2 and EC-Orange systems deployed before June 29th, 2015. If this vulnerability is exploited, a user of the affected shopping website may obtain other users' information by sending a crafted HTTP request.

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 confidence

Authorization bypass vulnerability in EC-CUBE (versions 2.11.0-2.12.2) and EC-Orange e-commerce platforms where user-controlled input in HTTP requests is used to improperly access other users' personal information, allowing attackers to view sensitive customer data without authentication.

MitigationUpgrade to patched versions of EC-CUBE and EC-Orange released after June 29th, 2015, or apply vendor-supplied security patches to address the authorization flaw.

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
Ec CubeApplication
Affected:= 2.11.0= 2.11.1= 2.11.2= 2.11.3= 2.11.4= 2.11.5= 2.12.0= 2.12.1= 2.12.2

CVSS 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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if EC-CUBE or EC-Orange is installed
    Check the application documentation, footer, or source code for EC-CUBE or EC-Orange branding and version strings. Common locations include the HTML source, administration panel, or version configuration files.
    Affected if The system is running EC-CUBE or EC-Orange e-commerce platform
  2. Check the installed EC-CUBE version number
    Locate the version file or administration panel that displays the EC-CUBE version. Common paths include /data/class/helper/SC_Utils.php or the administration console under System Settings. Compare the version against 2.11.0 through 2.12.2.
    Affected if The installed version is 2.11.0, 2.11.1, 2.11.2, 2.11.3, 2.11.4, 2.11.5, 2.12.0, 2.12.1, or 2.12.2
  3. Verify customer data endpoints are accessible
    Test HTTP endpoints that handle personal information such as order history, customer profiles, or address books. Attempt to manipulate user-controlled parameters (such as customer IDs or order IDs) in requests to access data belonging to other users without authentication.
    Affected if HTTP parameter manipulation allows unauthorized access to other users' personal data
  4. Check if the application uses proper session authorization
    Review application code for customer data retrieval functions. Examine whether user input is directly used in queries without verifying session ownership or proper authorization checks.
    Affected if Customer data queries rely on user input without validating the session user owns the requested data

If the system runs EC-CUBE or EC-Orange versions 2.11.0 through 2.12.2 and exposes customer data endpoints that accept user-controlled input without proper authorization validation, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to patched versions of EC-CUBE and EC-Orange released after June 29th, 2015, or apply vendor-supplied security patches to address the authorization flaw.

Recommended fix Moderate confidence

EC-CUBE 2.12.3 or later

  1. 1. Verify current EC-CUBE installation version by checking the version file or admin panel.
  2. 2. Backup the entire database and all files before performing any upgrade.
  3. 3. Download EC-CUBE version 2.12.3 or later from the official EC-CUBE website (www.ec-cube.net).
  4. 4. Extract the new version files and replace the existing application files, preserving local configuration files and any custom modifications.
  5. 5. Run any database migration scripts included in the new version.
  6. 6. Clear all cache files in the data/cache and data/templates_c directories.
  7. 7. Verify the application functions correctly by testing the shopping cart, user login, and order processes.
  8. 8. Confirm the vulnerability is remediated by attempting the crafted HTTP request described in the CVE (manipulating the customer_id parameter).
Caveat Custom templates or modifications made for 2.11.x may require adjustments for 2.12.x compatibility; thoroughly test all custom functionality after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ec Cube Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0808 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0808 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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