Security readout for executives and security teams
Plain-English summary
This CVE describes SQL injection in Online Banking System v1.0 through the cust_id parameter on the funds-transfer page. If an organization runs this code or a fork, an unauthenticated network attacker could potentially read, change, or disrupt backend data. The public CVE data does not identify a vendor patch or confirmed real-world exploitation.
Executive priority
Treat this as urgent only for environments running the named banking application or a fork. The theoretical impact is severe because banking data and transactions may be affected, but the source bundle does not prove broad product exposure, a vendor patch, or active exploitation.
Technical view
CVE-2022-40113 is CWE-89 SQL injection in /net-banking/send_funds.php via cust_id. The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction. Affected metadata is incomplete, listing vendor/product/version as n/a despite the title naming Online Banking System v1.0.
Likely exposure
Exposure is likely limited to deployments of the referenced Online Banking System v1.0 codebase or derived forks, especially if /net-banking/send_funds.php is internet-accessible. Because CPE and vendor fields are absent, teams must verify by application inventory, repository lineage, route presence, and code review rather than product matching alone.
Exploitation context
The CVSS vector indicates remotely reachable, unauthenticated attack surface with high confidentiality, integrity, and availability impact. The bundle marks KEV as false, and no provided source confirms exploitation in the wild. Public GitHub references may increase awareness, but they are not evidence of active exploitation.
Researcher notes
The strongest evidence is the CVE record plus GitHub issue/report references. The affected product metadata is weak, so enrichment should focus on repository lineage, deployed route discovery, and source review. Do not infer other banking platforms are affected without matching code or vendor confirmation.
Mitigation direction
- Identify whether any deployed application uses this Online Banking System code or fork.
- Check upstream project issue and repository history for maintainer guidance or fixes.
- Restrict public access to the affected funds-transfer route until risk is resolved.
- If maintaining the code, use parameterized queries and strict server-side validation.
- Review database permissions used by the web application for least privilege.
Validation and detection
- Inventory public routes and confirm whether /net-banking/send_funds.php exists.
- Review handling of cust_id for dynamic SQL construction.
- Run only authorized, non-destructive validation in a staging environment.
- Inspect web and database logs for unusual requests to send_funds.php.
- Confirm remediation with regression tests covering cust_id input handling.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-40113 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/zakee94/online-banking-system/issues/18CVE reference · x_refsource_MISC
- https://github.com/0clickjacking0/BugReport/blob/main/online-banking-system/sql_injection3.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.