What is the CVSS score of CVE-2026-31070?

CVE-2026-31070 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Pharmacy Management System are affected by CVE-2026-31070?

LalanaChami Pharmacy Management System contains a critical unauthenticated privilege escalation vulnerability (CVE-2026-31070) allowing any remote attacker to create administrator accounts with a…

How to fix or mitigate CVE-2026-31070?

Within 24 hours: disable the /api/user/signup endpoint or implement mandatory server-side role validation rejecting all client-supplied role parameters; audit all user accounts created in the past 30 days for unauthorized administrative privileges. Within 7 days: contact LalanaChami for emergency guidance; review API access logs for exploitation attempts and suspicious account creation patterns. Within 30 days: conduct full security assessment of authentication and authorization mechanisms; implement role-based access controls with server-side enforcement.

Pharmacy Management System CVE-2026-31070

EUVD-2026-30945 CRITICAL

Improper Privilege Management (CWE-269)

2026-05-19 mitre

GHSA-qg5w-7c3j-rfjc

Privilege Escalation N A

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 20, 2026 - 14:23 vuln.today

CVSS changed

May 20, 2026 - 14:22 NVD

9.8 (CRITICAL)

CVE Published

May 19, 2026 - 00:00 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

The 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

AnalysisAI

Privilege escalation in LalanaChami Pharmacy Management System (commit 5c3d028) allows any remote unauthenticated attacker to register a new account with administrator privileges by simply including a role parameter in the signup request body. The /api/user/signup endpoint trusts client-supplied role values without server-side validation, granting full administrative access in a single HTTP call. No public exploit identified at time of analysis, and EPSS is very low (0.04%), but the trivial nature of the flaw means weaponization is straightforward once anyone notices the gist already documenting the issue.

Technical ContextAI

The affected software is a Node.js/Express-based pharmacy application maintained on GitHub under LalanaChami/Pharmacy-Mangment-System. The vulnerability falls under CWE-269 (Improper Privilege Management): the signup route handler in backend/routes/user.js accepts the request body verbatim and persists whatever role string the client supplies, rather than forcing newly registered users to a default low-privilege role and gating administrative roles behind an authenticated, authorized provisioning flow. This is a classic mass-assignment / parameter tampering issue where the server-side data model exposes a privileged attribute to an untrusted input boundary.

RemediationAI

No vendor-released patch identified at time of analysis - the project does not appear to have published a tagged fix release. Operators should immediately modify backend/routes/user.js to strip or ignore any client-supplied role field on the /api/user/signup endpoint and force newly created accounts to a hardcoded non-privileged default role, with administrative role assignment handled only by an authenticated admin via a separate endpoint with proper authorization checks. As compensating controls until code is patched: place the signup endpoint behind an authenticated reverse-proxy ACL or remove the endpoint entirely if self-registration is not required (side effect: blocks all new user onboarding), or add a WAF/middleware rule that rejects POSTs to /api/user/signup containing a 'role' key in the JSON body (side effect: may break legitimate clients if they ever needed to send role data, though they should not). Audit the user table for any accounts created with administrative roles since deployment and revoke or delete unauthorized admins. Reference advisories: https://nvd.nist.gov/vuln/detail/CVE-2026-31070 and the disclosure gist https://gist.github.com/nedlir/22bf6d1a3a07209be3e343744bc81d51.