A vulnerability was identified in PHPGurukul Bank Locker Management System 1.0. This affects an unknown function of the file /blms/view-assign-locker.php. The manipulation of the argument ltid leads to authorization bypass. The attack may be initiated remotely. The exploit is publicly available and might be used.
CVE-2026-90517
Score 5.3 from GitHub Security Advisory published 2026-09-13. a secondary CVSS source baseline 5.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
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
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 computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
September 13, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 13, 2026PHP Project | PHP Projects Ideas | PHP Latest tutorial | Python Project
https://phpgurukul.com/Bank Locker Management System 1.0 - Unauthenticated Sensitive Information Disclosure in `/view-assign-locker.php` · Issue #2 · wakakakaaaaha/vuln · GitHub
https://github.com/wakakakaaaaha/vuln/issues/2Vendor Advisories for CVE-2026-90517(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 24× in last 7d / 28× 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-20 20:16 UTCEPSS rescore
- 2026-09-20 06:21 UTCEG score recompute
- 2026-09-20 06:20 UTCGHSA enrichment
- 2026-09-19 08:38 UTCEG score recompute
- 2026-09-19 08:38 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 10:54 UTCEG score recompute
- 2026-09-18 10:54 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 13:12 UTCGHSA enrichment
- 2026-09-16 15:30 UTCEG score recompute
- 2026-09-16 15:30 UTCGHSA enrichment
- 2026-09-16 15:18 UTCNVD updateCVSS v4 → 5.5
- 2026-09-16 14:26 UTCEG score recompute
- 2026-09-16 14:26 UTCGHSA enrichment
- 2026-09-16 14:25 UTCMITRE cvelistV5CVSS v4 → 6.9
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 18:49 UTCEG score recompute
- 2026-09-15 18:49 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 21:07 UTCGHSA enrichment
- 2026-09-14 10:00 UTCEG score recompute
- 2026-09-14 10:00 UTCGHSA enrichment
- 2026-09-13 12:18 UTCEG score recompute
Show 3 moreShow fewer
- 2026-09-13 12:18 UTCNVD updateCVSS v4 → 5.5
- 2026-09-13 11:55 UTCEG score recompute
- 2026-09-13 11:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-90517?
When was CVE-2026-90517 disclosed?
Is CVE-2026-90517 actively exploited?
What is the CVSS score of CVE-2026-90517?
How do I remediate CVE-2026-90517?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-90517
Is Your Infrastructure Affected by CVE-2026-90517?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.