LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35387: Hospital Management System v 4.0 is vulnerable to SQL Injection via file:hospital/hms/admin/view-patient.php.

Hospital Management System v 4.0 is vulnerable to SQL Injection via file:hospital/hms/admin/view-patient.php.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-35387 is a SQL injection issue in the referenced Hospital Management System v4.0 admin patient-view page. A logged-in attacker could potentially read, change, or disrupt backend database data. The source bundle does not identify a vendor patch or active exploitation.

Executive priority

Treat as a high-priority application risk if this system is deployed. The main business concern is unauthorized access to patient or operational data, but urgency depends on whether the vulnerable application is present and reachable.

Technical view

The issue is CWE-89 SQL injection in hospital/hms/admin/view-patient.php. CVSS 3.1 is 8.8, with network access, low attack complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to deployments of Hospital Management System v4.0 or derived codebases containing the vulnerable admin view-patient.php behavior. The CVE metadata lists affected vendor and product as n/a, so asset owners must verify by application name, version, and code path.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates remote exploitation is plausible where an attacker has low-privileged application access and can reach the affected admin page.

Researcher notes

Evidence is sparse: the CVE names the vulnerable file and SQL injection class, but affected CPEs, fixed versions, and patch details are not supplied. Focus validation on code provenance, version confirmation, route exposure, and authenticated role reachability.

Mitigation direction

  • Check project or vendor guidance for an official fixed release or patch.
  • Restrict access to the admin interface to trusted users and networks.
  • If maintaining the code, use parameterized queries for database access.
  • Review logs for suspicious admin patient-view requests.
  • Back up the database before applying application changes.

Validation and detection

  • Inventory any deployments of Hospital Management System v4.0 or forks.
  • Confirm whether hospital/hms/admin/view-patient.php exists in deployed code.
  • Review the patient-view database query handling for unsafe input concatenation.
  • Verify admin routes require authentication and least-privilege access.
  • Use authorized, non-destructive testing only; avoid production impact.
Prepared
Confidence
medium
Sources
4

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.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-2021-35387 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-35387Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.