Quick answers
- Is CVE-2026-90519 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90519 being exploited in the wild.
- How severe is CVE-2026-90519?
- 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-90519?
- 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-90519 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-90519?
- 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
An unrestricted file upload vulnerability exists in /blms/banker/add-locker-form.php where the addressproof file upload parameter lacks extension validation (the validation block is commented out in the code), while the photo parameter is properly validated. An authenticated attacker with valid banker or sub-banker credentials can upload a PHP webshell as the addressproof parameter, which is saved with a predictable filename (MD5 hash + timestamp + extension) to the web-accessible /blms/banker/addressproof/ directory. No MIME-type validation or .htaccess restrictions prevent execution. The attacker can then locate the uploaded file by brute-forcing the timestamp and execute arbitrary PHP code with web-server privileges, achieving remote code execution and full system compromise.
Affected products
- PHPGurukul Bank Locker Management System 1.0
Timeline
- 2026-07-31: disclosed
- 2026-09-13: advisory