CVE-2023-4443
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 · uneditedA vulnerability classified as critical has been found in SourceCodester Free Hospital Management System for Small Practices 1.0/5.0.12. Affected is an unknown function of the file vm\doctor\edit-doc.php. The manipulation of the argument id00/nic/oldemail/email/spec/Tele leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-237564.
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 confidenceSQL injection vulnerability in SourceCodester Free Hospital Management System for Small Practices allows remote attackers to inject malicious SQL queries through multiple parameters (id00, nic, oldemail, email, spec, Tele) in the edit-doc.php file without proper input sanitization.
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= 1.0CVSS 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 the application installationLocate the web root directory and identify if SourceCodester Free Hospital Management System for Small Practices is installed. Look for common paths like /var/www/html/, /htdocs/, or C:\xampp\htdocs\. Search for recognizable files such as index.php or login.php from this application.Affected if The application is not found in the environment, meaning the system is not affected.
-
Verify the affected versionCheck the application version. In the web root, look for a version file, about page, or check the footer of the main page for version information. Compare against version 1.0.Affected if The installed version is exactly 1.0, matching the affected version.
-
Locate the vulnerable edit-doc.php fileNavigate to the application directories and search for the file edit-doc.php. Common paths include /admin/, /doctor/, or /includes/ subdirectories within the web root.Affected if The file edit-doc.php exists in the application installation.
-
Inspect the vulnerable code for SQL injection pointsOpen edit-doc.php in a text editor and search for the parameters id00, nic, oldemail, email, spec, and Tele. Examine how these parameters are used in database queries - look for direct string concatenation or lack of prepared statements.Affected if The code shows these parameters being used in SQL queries without parameterized queries, prepared statements, or input sanitization functions.
-
Determine if the doctor editing functionality is accessibleAttempt to access the edit-doc.php file through the web browser or verify via web server logs that this endpoint is reachable. Check if there are authentication requirements or IP restrictions on this page.Affected if The edit-doc.php page is accessible without additional security controls beyond basic authentication, and the application processes user input through the vulnerable parameters.
A user is affected if they have version 1.0 of SourceCodester Free Hospital Management System for Small Practices installed with the edit-doc.php file containing the vulnerable SQL query implementations for the id00, nic, oldemail, email, spec, or Tele parameters.
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 parameterized queries/prepared statements for all database operations in the affected file. Given the critical severity and public exploit availability, consider restricting network access or disabling the doctor editing functionality until the patch is applied.
- Consultation4.0 h
- Implementation10.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4443 — 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-2023-4443 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