CVE-2026-7632
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 was determined in code-projects Online Hospital Management System 1.0. This affects an unknown function of the file /viewappointment.php. This manipulation of the argument delid causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.
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 · moderate confidenceA SQL injection vulnerability exists in the Online Hospital Management System 1.0's viewappointment.php file. The delid parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries into the database. This could enable unauthorized data access, modification, or potentially remote code execution depending on database configuration.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 Online Hospital Management System 1.0 installationSearch the web root directory for files containing 'Online Hospital Management System' or check application documentation to verify the product name and version 1.0 is deployedAffected if The system is running Online Hospital Management System version 1.0
-
Locate the vulnerable viewappointment.php fileSearch the web application directory tree for the file viewappointment.php, typically found in the main application folder or a 'patient' or 'appointment' subdirectoryAffected if The file viewappointment.php exists in the deployed application
-
Verify the delid parameter is in useExamine the viewappointment.php file and look for the delid parameter being used in GET or POST requests (search for '$_GET' or '$_POST' with 'delid')Affected if The delid parameter is accepted as user input without evident sanitization routines
-
Check for lack of parameterized queriesOpen viewappointment.php and inspect the database query code around the delid parameter; look for direct string concatenation or interpolation of the delid value into SQL statements without using prepared statements or bindingAffected if SQL queries incorporate the delid parameter directly without parameterized binding or escaping functions
-
Confirm database connectivityVerify the application connects to a MySQL or other SQL database by checking database configuration files or the presence of mysqli/PDO connection code in the applicationAffected if The application uses a SQL database and the vulnerable code path is reachable
A user is affected if they run Online Hospital Management System 1.0 with the viewappointment.php file present and the delid parameter is processed in SQL queries without parameterized prepared statements.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the delid parameter in viewappointment.php, and perform input validation on all user-supplied parameters. Conduct a broader audit of the application for similar SQL injection vulnerabilities.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7632 — 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-2026-7632 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