Quick answers
- Is CVE-2026-90518 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90518 being exploited in the wild.
- How severe is CVE-2026-90518?
- Medium severity, with a CVSS score of 6.3, published 13 September 2026.
- Which products and versions are affected?
- Phpgurukul Bank Locker Management System 1.0.
- Is there a fix for CVE-2026-90518?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-90518 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-90518?
- Check whether you run Phpgurukul Bank Locker Management System at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a broken access control issue (CWE-639) in the Bank Locker Management System version 1.0, specifically in the file sidebar.php and related endpoints such as /banker/manage-subadmins.php. The flaw stems from missing server-side validation of the UserType parameter, allowing an authenticated attacker to manipulate role checks. An attacker with sub-admin credentials can craft requests to bypass authorization controls and perform administrative actions, such as creating or modifying user roles. The attack requires network access and valid authentication but no additional user interaction. A public exploit has been released and the vulnerability may be exploited in the wild. No patch information is currently available.
Affected products
- PHPGurukul Bank Locker Management System 1.0
Timeline
- 2026-09-13: disclosed
- 2026-09-13: other: Public exploit released