LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69949: kishan0725 Hospital Management System 4.0 is vulnerable to SQL Injection in check_availability.php via the...

kishan0725 Hospital Management System 4.0 is vulnerable to SQL Injection in check_availability.php via the parameters emailid and email.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Hospital Management System 4.0 reportedly allows unauthenticated internet users to manipulate database queries through two email-related inputs. Successful exploitation could expose, alter, or disrupt limited application data. Healthcare deployments may face elevated business impact because operational and personal information could be involved, although the supplied evidence does not establish the specific data accessible.

Executive priority

Treat confirmed internet-facing deployments as a high-priority remediation item. Prioritize systems handling patient, identity, scheduling, billing, or operational data. If exposure cannot be ruled out promptly, restrict the endpoint while technical teams validate the version and implementation. There is no supplied evidence requiring an emergency incident declaration solely from this CVE record.

Technical view

CVE-2025-69949 is a CWE-89 SQL injection in check_availability.php through the email and emailid parameters. The CVSS 3.1 score is 7.3: network-accessible, low complexity, requiring neither privileges nor user interaction, with low confidentiality, integrity, and availability impacts. The structured affected-product fields are unspecified, while the description identifies kishan0725 Hospital Management System 4.0.

Likely exposure

Exposure is most likely where Hospital Management System 4.0 runs check_availability.php and untrusted users can reach it. Internet-facing instances warrant immediate review. The source bundle provides no CPEs, deployment prevalence, authentication context, or reliable product identifiers, so organizations should confirm exposure by application name, version, endpoint, and code provenance.

Exploitation context

The conditions suggest straightforward remote exploitation because no authentication, user interaction, or unusual access is required. However, the supplied record is not in CISA KEV and provides no evidence of active exploitation, public weaponization, or observed attacks. The GitHub references document the reported vulnerable inputs but do not establish exploitation prevalence.

Researcher notes

The record has material attribution gaps: affected vendor, product, versions, and CPE fields are listed as n/a despite the description naming kishan0725 Hospital Management System 4.0. Assessment rests on the description, CVSS vector, CWE classification, and two TaintRadar references. Patch availability, vulnerable code boundaries, database engine, authentication behavior, and real-world exploitation remain unconfirmed.

Mitigation direction

  • Identify and restrict externally reachable check_availability.php endpoints pending remediation.
  • Check the project maintainer or vendor guidance for a supported correction or updated release.
  • Have developers eliminate unsafe SQL construction using approved parameterized database operations.
  • Apply least-privilege database permissions to limit potential data access and modification.
  • Monitor application and database logs for suspicious requests involving the affected parameters.

Validation and detection

  • Inventory Hospital Management System deployments and confirm whether version 4.0 is present.
  • Verify whether check_availability.php accepts the email or emailid parameters.
  • Review the endpoint code for untrusted input entering dynamically constructed SQL.
  • Test remediation safely in an authorized non-production environment without accessing real patient data.
  • Confirm monitoring detects abnormal requests and database errors associated with the endpoint.
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-2025-69949 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
7.3 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

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
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2025-69949Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

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

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
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.