CVE-2018-19853
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 hitshop through 2014-07-15. There is an elevation-of-privilege vulnerability (that allows control over the whole web site) via the admin.php/user/add URI because a storekeeper account (which is supposed to have only privileges for commodity management) can add an administrator account.
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 confidenceHitShop allows storekeeper accounts (limited to commodity management) to access admin.php/user/add and create administrator accounts, achieving privilege escalation to full site control.
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<= 2014-07-15CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 HitShop installation and versionLocate the HitShop installation directory and check version files (such as version info in configuration files, headers, or a dedicated version file) to determine if the installed version is at or before the 2014-07-15 buildAffected if The installed version is HitShop Project Hitshop at or below the 2014-07-15 release date
-
Confirm admin.php/user/add endpoint existsVerify the presence of the admin.php script and its user/add functionality by checking the application file structure or attempting to access the endpoint via web request (if authorized)Affected if The admin.php/user/add endpoint exists in the HitShop installation
-
Check storekeeper role configurationExamine the user role definitions in the HitShop database or configuration files to confirm that a storekeeper role exists and document its assigned permissionsAffected if A storekeeper role with limited commodity management permissions is defined in the system
-
Verify if storekeeper can access user creationReview role-based access control (RBAC) settings to determine whether the storekeeper role is permitted to access admin.php/user/add or create new usersAffected if The storekeeper role has permission to access user creation functionality or the RBAC check on admin.php/user/add is missing or inadequate
Your environment is affected if you are running HitShop Project Hitshop at version 2014-07-15 or earlier AND the storekeeper role can access the admin.php/user/add endpoint to create administrator accounts.
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 dataImplement role-based access control (RBAC) on admin.php/user/add to verify the requester has administrator privileges before allowing user creation, and remove user management capabilities from storekeeper role.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19853 — 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-2018-19853 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