dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-31071

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-19
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
API endpoints in LalanaChami Pharmacy Management System (commit 5c3d028) lack authentication middleware. Unauthenticated remote attackers can exploit this to dump all user records (including bcrypt password hashes) via /api/user/getUserData, modify drug inventory, and access private medical prescription data via /api/doctorOder.

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 confidence

API endpoints in the LalanaChami Pharmacy Management System lack authentication middleware, allowing unauthenticated remote attackers to access sensitive endpoints. The /api/user/getUserData endpoint exposes all user records including bcrypt password hashes, /api/doctorOder leaks private medical prescription data, and attackers can also modify drug inventory.

MitigationImplement authentication middleware on all API endpoints and ensure proper session/token validation is required before granting access to sensitive data or inventory modification functions.

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
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 LalanaChami Pharmacy Management System installation
    Search your web server logs, application directories, or container images for 'LalanaChami' or 'Pharmacy Management System' deployment artifacts
    Affected if The system is present in your environment
  2. Verify /api/user/getUserData endpoint exists
    Review your API routing configuration or attempt a GET request to /api/user/getUserData without providing any authentication tokens
    Affected if The endpoint responds with HTTP 200 and returns user data including password hashes
  3. Verify /api/doctorOder endpoint exists
    Review your API routing configuration or attempt a GET/POST request to /api/doctorOder without authentication
    Affected if The endpoint accepts requests without requiring auth and returns prescription data
  4. Confirm inventory API endpoints lack authentication
    Review API routes related to drug inventory (typically /api/inventory, /api/drugs, or similar paths) or test if they accept unauthenticated requests
    Affected if Inventory modification endpoints respond without authentication challenges
  5. Check API middleware configuration
    Inspect the application source code or API gateway configuration to verify whether authentication middleware is applied to the /api/ routes, specifically examining middleware chain order
    Affected if No authentication middleware is present in the API route handlers

If the LalanaChami Pharmacy Management System is deployed and any of the /api/user/getUserData, /api/doctorOder, or inventory endpoints are accessible without authentication tokens, the environment is affected by this vulnerability.

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

Implement authentication middleware on all API endpoints and ensure proper session/token validation is required before granting access to sensitive data or inventory modification functions.

Recommended fix Moderate confidence
  1. 1. Identify all unprotected API endpoints in the LalanaChami Pharmacy Management System, specifically /api/user/getUserData, /api/doctorOder, and any endpoints related to drug inventory management.
  2. 2. Implement authentication middleware that validates user credentials or session tokens before allowing access to these protected endpoints.
  3. 3. Ensure the authentication middleware is applied globally to all API routes that handle sensitive data (user records, medical prescriptions, inventory).
  4. 4. For the /api/user/getUserData endpoint specifically, restrict access so only authenticated administrators can retrieve user records and password hashes.
  5. 5. Add authorization checks to verify that authenticated users have appropriate permissions for the requested operation (e.g., only pharmacists should modify drug inventory).
  6. 6. Review and secure any additional API endpoints not explicitly mentioned in the vulnerability report that may also lack authentication.
  7. 7. Test all protected endpoints with both authenticated and unauthenticated requests to verify the fix is effective.
  8. 8. Consider implementing rate limiting and request logging to detect and prevent future unauthorized access attempts.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31071 — 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-2026-31071 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