CVE-2026-31070
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 · uneditedThe LalanaChami Pharmacy Management System (commit 5c3d028) allows unauthenticated remote attackers to escalate privileges by self-assigning an administrative role during registration. The /api/user/signup endpoint fails to validate the role parameter in the request body
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 confidenceThe LalanaChami Pharmacy Management System /api/user/signup endpoint accepts a role parameter in the request body without server-side validation, allowing any unauthenticated user to register with administrative privileges by simply including 'admin' or similar elevated role values in their registration request.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
CVSS:3.1/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.
-
Confirm LalanaChami Pharmacy Management System is deployedIdentify the application by checking web application fingerprints, headers, or by locating typical installation paths for this system. Check for references to 'LalanaChami' or 'Pharmacy Management' in the application.Affected if The system is running an instance of LalanaChami Pharmacy Management System.
-
Locate the signup endpointVerify the existence of the /api/user/signup endpoint by attempting to access it or reviewing API documentation/routes.Affected if The /api/user/signup endpoint is accessible and responds to requests.
-
Test role parameter acceptanceSend a POST request to /api/user/signup with a JSON body containing a 'role' parameter set to 'admin' or another privileged role, alongside required registration fields (username, password, email). Observe if the role is accepted without error.Affected if The endpoint accepts and processes a client-supplied role parameter without rejecting it.
-
Verify role assignment without validationAfter registration, query the created user account to confirm the role assigned matches what was submitted in the request rather than a default non-privileged role.Affected if The user account is created with the client-supplied role value, indicating no server-side validation is performed.
A user is affected if the /api/user/signup endpoint accepts and applies a client-supplied role parameter without server-side validation, allowing self-assignment of administrative privileges during registration.
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 server-side role validation on the signup endpoint to ignore or reject client-supplied role parameters, automatically assigning new users a default low-privilege role (e.g., 'user' or 'customer') and restricting role assignment to administrative functions only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31070 — 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-2026-31070 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