CVE-2022-46497
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 · uneditedHospital Management System 1.0 was discovered to contain a SQL injection vulnerability via the pat_number parameter at his_doc_view_single_patien.php.
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 confidenceSQL injection vulnerability in Hospital Management System 1.0 allows unauthenticated attackers to inject malicious SQL queries through the pat_number parameter in his_doc_view_single_patien.php, potentially enabling data exfiltration or complete database compromise.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Hospital Management System installationLocate the web application's root directory and confirm the presence of Hospital Management System files. Common locations include /var/www/html, /www, or C:\inetpub\wwwroot depending on the server OS.Affected if The Phpgurukul Hospital Management System is found on the server
-
Confirm exact version numberCheck for version information in the application. Look for a version file, about page, or header/footer files that display the version. Compare the installed version to the affected range.Affected if The installed version is exactly 1.0
-
Locate the vulnerable scriptSearch for the file his_doc_view_single_patien.php within the web application directory structure. This file typically resides in the doctor or admin section of the application.Affected if The file his_doc_view_single_patien.php exists in the application
-
Verify parameter handlingExamine the source code of his_doc_view_single_patien.php and locate the pat_number parameter usage. Check if the parameter is directly used in SQL queries without parameterized queries or input sanitization.Affected if The pat_number parameter is used in SQL queries without prepared statements or proper escaping
-
Test external accessibilityDetermine if the vulnerable script is accessible from the network. Check if the application requires authentication to access this endpoint or if it can be reached anonymously.Affected if The script is accessible without authentication
A system is affected if it runs Phpgurukul Hospital Management System version 1.0 with the vulnerable his_doc_view_single_patien.php script accessible and using unsanitized pat_number parameter in SQL queries.
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, implement strict input validation on the pat_number parameter, and apply the principle of least privilege to database accounts.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-46497 — 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-2022-46497 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