LiveActive security incident?Get immediate response
CVE Record

CVE-2020-22168: PHPGurukul Hospital Management System in PHP v4.0 has a SQL injection vulnerability in \hms\change-emaild.php.

PHPGurukul Hospital Management System in PHP v4.0 has a SQL injection vulnerability in \hms\change-emaild.php. Remote unauthenticated users can exploit the vulnerability to obtain database sensitive information.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-22168 is a reported SQL injection in PHPGurukul Hospital Management System in PHP v4.0. The CVE description says unauthenticated remote users may obtain sensitive database information through hms/change-emaild.php. For organizations using this application, the main business risk is exposure of patient, staff, or operational data.

Executive priority

Prioritize this if PHPGurukul HMS v4.0 is deployed, especially in healthcare environments. Sensitive database exposure from an unauthenticated web flaw can create operational, privacy, and regulatory impact.

Technical view

The reported flaw is SQL injection in hms/change-emaild.php in PHPGurukul Hospital Management System in PHP v4.0. The source bundle does not provide CVSS, CWE, affected CPEs, patch details, or exact vulnerable parameter information. Treat exposed instances as potentially high risk until vendor guidance or code review confirms status.

Likely exposure

Exposure is likely limited to organizations running PHPGurukul Hospital Management System in PHP v4.0, especially internet-facing hms deployments. The bundle does not identify other affected versions or products.

Exploitation context

The CVE description states remote unauthenticated exploitation is possible for database information disclosure. The bundle includes a public GitHub reference, but KEV is false and no cited source confirms active exploitation in the wild.

Researcher notes

Evidence is limited. The CVE record names the vulnerable file and version, but does not provide scoring, affected CPEs, patch status, or full technical root cause. Avoid broad version claims beyond v4.0 without vendor confirmation.

Mitigation direction

  • Check PHPGurukul or upstream guidance for a fixed release or official mitigation.
  • Restrict public access to affected hms routes until exposure is validated.
  • Prioritize upgrade or removal of PHPGurukul HMS v4.0 where still deployed.
  • Review application code for parameterized queries around email-change functionality.
  • Assess whether sensitive database records or credentials require rotation after suspected exposure.

Validation and detection

  • Inventory public and internal PHPGurukul HMS deployments.
  • Confirm whether any deployment is version 4.0.
  • Check whether hms/change-emaild.php exists and is reachable.
  • Review web and database logs for suspicious access to the email-change route.
  • Document whether vendor guidance or a fixed version is available.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-22168 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.