Online Medicine Ordering SystemApplication · Oretnom23

CVE-2024-46293

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-30
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
Sourcecodester Online Medicine Ordering System 1.0 is vulnerable to Incorrect Access Control. There is a lack of authorization checks for admin operations. Specifically, an attacker can perform admin-level actions without possessing a valid session token. The application does not verify whether the user is logged in as an admin or even check for a session token at all.

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

The Online Medicine Ordering System 1.0 fails to implement any authentication or authorization checks on admin functionality. The application does not validate session tokens or verify user identity before executing admin-level operations, allowing unauthenticated attackers to directly access and manipulate administrative functions.

MitigationImplement robust session management with token validation on all admin endpoints, enforce role-based access control (RBAC) to verify user privileges before executing administrative operations, and add authentication middleware across 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
Online Medicine Ordering SystemApplication
Affected:= 1.0

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version
    Check the application version displayed in the system (typically in the footer, about page, or admin dashboard) and confirm it is version 1.0 of Oretnom23 Online Medicine Ordering System
    Affected if The installed version is exactly 1.0 and matches the affected product name
  2. Verify admin endpoint accessibility
    Attempt to access common admin paths such as /admin/, /admin/dashboard, /admin/users, or /admin/medicines directly from an unauthenticated browser or using a tool like curl without providing any session cookies or credentials
    Affected if Admin pages load successfully without any authentication token, session cookie, or login redirect
  3. Inspect authentication enforcement
    Review the source code or configuration files for any middleware, filters, or logic that validates user identity before executing admin operations. Check for session validation routines or token checks in the admin controller files
    Affected if No session validation, token verification, or user identity checks are found in the admin functionality code
  4. Test admin operation execution
    Send a direct HTTP request to perform an admin-level action (such as adding/modifying users, medicines, or orders) without providing any authentication credentials or valid session
    Affected if The admin operation executes successfully and returns a success response without requiring authentication

The environment is affected if the installed system is Oretnom23 Online Medicine Ordering System version 1.0 AND admin functions can be accessed or executed without any authentication credentials, session token, or authorization check.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust session management with token validation on all admin endpoints, enforce role-based access control (RBAC) to verify user privileges before executing administrative operations, and add authentication middleware across the application.

Fix this in Online Medicine Ordering System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-46293 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-46293 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