Security readout for executives and security teams
Plain-English summary
A reported SQL injection flaw affects Hospital Management System 4.0. An internet-based attacker may be able to manipulate database queries without authentication or user interaction, potentially exposing or changing sensitive hospital data and disrupting service. The supplied sources do not identify a vendor patch.
Executive priority
Prioritize immediate exposure discovery and containment, especially for internet-accessible systems handling patient or operational data. Escalate confirmed deployments for urgent remediation and compromise review. The critical score supports rapid action, although active exploitation and an official fix are not established by the supplied evidence.
Technical view
CVE-2025-65340 is classified as CWE-89 in /betweendates-detailsreports.php. Its CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, producing a 9.8 score. This indicates remotely reachable, low-complexity, unauthenticated exploitation with potentially high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where Hospital Management System 4.0 deploys the affected PHP endpoint and attackers can reach it. Public internet exposure materially increases urgency. The structured affected-product fields are unspecified, so asset owners should confirm product identity and version locally.
Exploitation context
A public technical reference reports SQL injection evidence, but the supplied bundle does not establish exploitation in the wild. The CVE is not listed as KEV in the provided data. Treat proof-of-concept availability and active exploitation status as unconfirmed beyond the cited research.
Researcher notes
The record identifies a specific PHP endpoint and SQL injection class, while structured vendor, product, version, and CPE fields remain n/a. This metadata inconsistency limits confident inventory matching. The cited research should be reviewed defensively; independently verify affected builds and avoid interpreting publication as evidence of widespread exploitation.
Mitigation direction
- Identify deployments of Hospital Management System 4.0 and restrict access to the affected endpoint.
- Check the project or vendor guidance for an official patch or corrected release.
- Apply temporary network or application-layer restrictions until authoritative remediation is available.
- Protect database credentials using least privilege and rotate them if compromise is suspected.
- Review backups and incident-response readiness for sensitive records and service disruption.
Validation and detection
- Confirm whether /betweendates-detailsreports.php exists and is remotely reachable.
- Verify the installed product and version because structured affected-product metadata is incomplete.
- Review web, application, and database logs for anomalous requests or unexpected query activity.
- Use authorized, non-destructive testing to confirm remediation without exposing patient data.
- Recheck vendor or project guidance for newly published fixes and affected-version clarification.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupDatabase 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 lookupCVE-2025-65340 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/um-dsp/TaintRadar/blob/main/sql_injection_cves/hospitalmanagementsystemproject/20250811-hospital-management-system-betweendates-detailsreports.php-fromdate-sqli/20250811-hospital-management-system-betweendates-detailsreports.php-fromdate-sqli.md#injection-techniques-as-identified-by-sqlmapCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.