Unauthorized locker-record access via unchecked ltid
Published Sep 13, 2026 · Updated Sep 13, 2026
Authorization bypass in Bank Locker Management System 1.0 allows remote attackers to access assigned-locker records via ltid. The view-assign-locker.php endpoint uses the attacker-controlled ltid object identifier without a documented authorization check before returning an assignment. The route is remotely reachable; public evidence does not state whether a session is required or whether access extends beyond locker-assignment details.
Summary
What happened
Authorization bypass in Bank Locker Management System 1.0 allows remote attackers to access assigned-locker records via ltid. The view-assign-locker.php endpoint uses the attacker-controlled ltid object identifier without a documented authorization check before returning an assignment. The route is remotely reachable; public evidence does not state whether a session is required or whether access extends beyond locker-assignment details.
The record
- CVE
- CVE-2026-90517
- Published
- Sep 13, 2026
- Updated
- Sep 13, 2026
- Vendor
- Projectworlds
- Product
- Bank Locker Management System
- Classifications
- T1190
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 13, 2026CVE publishedPublication date reported by the CVE source.
- Sep 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- VulDB view-assign-locker.php proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo