Security readout for executives and security teams
Plain-English summary
CVE-2022-40122 is a critical SQL injection in Online Banking System v1.0. An unauthenticated network attacker may be able to manipulate database queries through the cust_id parameter in /net-banking/edit_customer_action.php, risking customer data exposure, tampering, or service disruption. The source bundle does not identify an official vendor fix.
Executive priority
Prioritize this as urgent if the application is deployed, internet-facing, or handles real customer banking data. The critical score reflects potential full data compromise without authentication. If the system is only a lab, demo, or unused fork, urgency is lower but remediation should still prevent accidental exposure.
Technical view
The record maps to CWE-89 with CVSS 3.1 score 9.8: network, low complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. The vulnerable input is cust_id on /net-banking/edit_customer_action.php. Affected vendor/product metadata is incomplete in CVE fields.
Likely exposure
Exposure is likely limited to deployments of the referenced Online Banking System v1.0 codebase, especially if the net-banking path is reachable from untrusted networks. Organizations should not infer exposure from CPE matching because no CPEs are provided.
Exploitation context
The bundle includes public GitHub references describing the issue, but KEV is false and no cited source here confirms active exploitation in the wild. Treat public technical disclosure as increasing opportunistic risk, while distinguishing it from confirmed exploitation.
Researcher notes
Evidence is narrow but specific: one endpoint and parameter are named, with CWE-89 and a critical CVSS vector. The CVE affected metadata lists vendor and product as n/a, so researchers should validate against source lineage and deployed code rather than relying on asset scanners alone.
Mitigation direction
- Check the project or maintainer guidance for a fixed release or patch.
- Restrict external access to affected banking administration paths where feasible.
- Review and harden database input handling for cust_id and similar parameters.
- Prioritize parameterized queries and server-side validation in any local remediation.
- Increase monitoring for suspicious database errors or unexpected customer record changes.
Validation and detection
- Inventory deployments of Online Banking System v1.0 or forks of the referenced project.
- Confirm whether /net-banking/edit_customer_action.php is present and reachable.
- Review code handling of the cust_id parameter for unsafe SQL construction.
- Check web and database logs for anomalous requests to the affected endpoint.
- Verify any vendor or local patch removes unsafe query construction.
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-40122 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/15CVE reference · x_refsource_MISC
- https://github.com/0clickjacking0/BugReport/blob/main/online-banking-system/sql_injection10.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.