Database read and modification via injectable cust_id
Published Sep 23, 2022 · Updated May 22, 2025
SQL injection in Online Banking System 1.0 allows remote attackers to read, modify, or delete database data via a crafted cust_id value. The /net-banking/delete_customer.php handler incorporates cust_id into an SQL statement without neutralizing SQL syntax, so crafted input changes the database command. No authentication or user interaction is required; database-account privileges bound the exposed records and operations.
Summary
What happened
SQL injection in Online Banking System 1.0 allows remote attackers to read, modify, or delete database data via a crafted cust_id value. The /net-banking/delete_customer.php handler incorporates cust_id into an SQL statement without neutralizing SQL syntax, so crafted input changes the database command. No authentication or user interaction is required; database-account privileges bound the exposed records and operations.
The record
- CVE
- CVE-2022-40117
- Published
- Sep 23, 2022
- Updated
- May 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- sql_injection2.md 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