CVE-2014-4919
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 Professional Edition before 4.7.13 and 4.8.x before 4.8.7, Enterprise Edition before 5.0.13 and 5.1.x before 5.1.7, and Community Edition before 4.7.13 and 4.8.x before 4.8.7 allow remote attackers to assign users to arbitrary dynamical user groups.
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 confidenceOXID eShop before versions 4.7.13/4.8.7 and 5.0.13/5.1.7 contains a broken access control vulnerability in the dynamical user group assignment functionality. Remote attackers can exploit missing authorization checks to assign arbitrary users to any dynamical user group, enabling privilege escalation within the application.
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.7.13>= 4.8.0, < 4.8.7< 5.0.13>= 5.1.0, < 5.1.7CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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.
-
Determine installed OXID eShop versionLocate the version file in the OXID installation directory (commonly version.php in the core directory or check the admin panel footer for the version number)Affected if The installed version falls within < 4.7.13, >= 4.8.0 and < 4.8.7, < 5.0.13, or >= 5.1.0 and < 5.1.7
-
Identify dynamical user group functionalityLog into the OXID admin panel and navigate to User Management > User Groups. Look for any user groups configured with dynamic assignment rules (criteria-based automatic membership)Affected if Dynamical user groups exist in the system and the application handles user-group assignments through this feature
-
Verify authorization on group assignment requestsExamine the HTTP requests and application code responsible for adding users to dynamical user groups. Confirm whether the application validates user permissions before allowing a user to be assigned to a groupAffected if The group assignment endpoint accepts requests without validating that the requester has administrative privileges to modify group memberships
-
Check for unexpected group assignmentsReview the database tables storing user-group relationships (typically oxobject2group or similar) for any user-to-group mappings that were not created by an administrator through proper admin channelsAffected if Users are found assigned to dynamical groups without corresponding admin audit trails or authorization logs
You are affected if your installed OXID eShop version is within the vulnerable ranges AND the dynamical user group assignment feature is in use, with no external access controls restricting the vulnerable endpoint.
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 data4.7.134.8.75.0.13
Upgrade OXID eShop to the patched versions (4.7.13/4.8.7 for Professional/Community Edition, 5.0.13/5.1.7 for Enterprise Edition) or later. If immediate patching is not possible, restrict access to user group management interfaces via web server configuration or access control lists.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4919 — 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-2014-4919 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