A weakness has been identified in gedelumbung HospitalManagement up to c2d45543789a3887067d3915f69d44cfc2cf76a8. This vulnerability affects unknown code. This manipulation causes cross-site request forgery. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-93531
Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-09-18. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (2)
Auto-updated Sep 18, 2026GitHub - gedelumbung/HospitalManagement: Simple Hospital Management System · GitHub
https://github.com/gedelumbung/HospitalManagement/CSRF protection disabled in CodeIgniter config; every admin POST endpoint is forgeable · Issue #6 · gedelumbung/HospitalManagement · GitHub
https://github.com/gedelumbung/HospitalManagement/issues/6Vendor Advisories for CVE-2026-93531(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 21:11 UTCEG score recompute
- 2026-09-19 21:11 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEG score recompute
- 2026-09-18 19:27 UTCGHSA enrichment
- 2026-09-18 17:26 UTCEG score recompute
- 2026-09-18 17:25 UTCNVD updateCVSS v4 → 2.1
- 2026-09-18 16:29 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-09-18 16:27 UTCEG score recompute
- 2026-09-18 16:24 UTCNVD updateCVSS v4 → 2.1
- 2026-09-18 15:24 UTCEG score recompute
- 2026-09-18 15:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-93531?
When was CVE-2026-93531 disclosed?
Is CVE-2026-93531 actively exploited?
What is the CVSS score of CVE-2026-93531?
How do I remediate CVE-2026-93531?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93531
Is Your Infrastructure Affected by CVE-2026-93531?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.