Cyber Resilience

CVE-2024-7753

Oretnom23 Clinic\'S Patient Management System 1.0

Public PoC
Published
14 August 2024
Modified
19 August 2024
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0088 56th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2024-7753 is a medium-severity Forced Browsing (CWE-425) vulnerability in Oretnom23 Clinic\'S Patient Management System. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability was found in SourceCodester Clinics Patient Management System 1.0. It has been declared as problematic. This vulnerability affects unknown code of the file /user_images/. The manipulation leads to direct request. The attack can be initiated remotely. The exploit…

more

has been disclosed to the public and may be used.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-7930Same product: Oretnom23 Clinic\'S Patient Management System
CVE-2024-6969Same product: Oretnom23 Clinic\'S Patient Management System
CVE-2024-7645Same product: Oretnom23 Clinic\'S Patient Management System
CVE-2024-7494Same product: Oretnom23 Clinic\'S Patient Management System
CVE-2023-1035Same product: Oretnom23 Clinic\'S Patient Management System
CVE-2024-7454Same product: Oretnom23 Clinic\'S Patient Management System
CVE-2024-8565Same product: Oretnom23 Clinic\'S Patient Management System
CVE-2024-7750Same product: Oretnom23 Clinic\'S Patient Management System
CVE-2024-7754Same product: Oretnom23 Clinic\'S Patient Management System
CVE-2024-7841Same product: Oretnom23 Clinic\'S Patient Management System

Affected Assets

oretnom23
clinic\'s patient management system
1.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 directly requires enforcement of authorizations for access to resources such as URLs, scripts, and files, structurally preventing forced browsing.

AC-24 requires that access-control decisions be applied to every request, addressing the missing enforcement on restricted URLs.

AC-6 requires restricting authorizations to the minimum needed, reducing the set of resources that must be protected against direct requests.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Directly requires policy-driven definition, enforcement, and review of authorizations on resources such as URLs.

PR.IR-01 mostly match
prevents

Protects environments from unauthorized logical access, which includes preventing direct requests to restricted paths.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.

prevents

Information access restriction implements the technical enforcement that directly blocks unauthorized direct requests.

prevents

Access control policy directly requires authorization checks on all resources, preventing forced browsing.

degrades

Managing access rights ensures every URL/script/file is explicitly authorized, mitigating direct request attacks.

degrades

Privileged access rights control enforces least-privilege checks on restricted endpoints.

prevents

Secure SDLC can include authorization design, yet the control itself does not guarantee runtime enforcement.

References