Unauthenticated database access via lockersize SQL injection
Published Mar 24, 2025 · Updated Mar 24, 2025
SQL injection in Bank Locker Management System 1.0 allows remote attackers to alter database queries through the lockersize parameter. The edit-locker.php handler uses the user-controlled lockersize value in a database operation without neutralizing SQL syntax, allowing the supplied value to change the query. No authentication or user interaction is required, and successful injection grants read or write access to application database records.
Summary
What happened
SQL injection in Bank Locker Management System 1.0 allows remote attackers to alter database queries through the lockersize parameter. The edit-locker.php handler uses the user-controlled lockersize value in a database operation without neutralizing SQL syntax, allowing the supplied value to change the query. No authentication or user interaction is required, and successful injection grants read or write access to application database records.
The record
- CVE
- CVE-2025-2681
- Published
- Mar 24, 2025
- Updated
- Mar 24, 2025
- Vendor
- Projectworlds
- Product
- Bank Locker Management System
- Classifications
- CWE-74, CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2025CVE publishedPublication date reported by the CVE source.
- Mar 24, 2025Record 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
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
- ARPANET-cyber GitHub issue 10 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