LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40117: Online Banking System v1.0 was discovered to contain a SQL injection vulnerability via the cust_id paramete...

Online Banking System v1.0 was discovered to contain a SQL injection vulnerability via the cust_id parameter at /net-banking/delete_customer.php.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-40117 is a critical SQL injection report affecting Online Banking System v1.0. A vulnerable customer deletion parameter could let an unauthenticated remote attacker affect banking data confidentiality, integrity, and availability if the application is deployed as described.

Executive priority

Treat as urgent if this online banking code is in production or internet reachable. The business risk is direct compromise or disruption of customer banking records. If the product is not used, document non-exposure and monitor for code reuse.

Technical view

The CVE describes CWE-89 SQL injection through the cust_id parameter in /net-banking/delete_customer.php. The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction. Structured affected CPE data is not provided.

Likely exposure

Exposure is most likely where Online Banking System v1.0, or code derived from it, is deployed and the /net-banking/delete_customer.php route is reachable. The CVE bundle does not identify vendor CPEs, hosted-service exposure, or a confirmed patch level.

Exploitation context

The CVSS vector indicates easy remote exploitability in principle, but the bundle does not show CISA KEV listing or confirmed active exploitation. Public GitHub references exist, so defenders should assume technical details may be accessible.

Researcher notes

Evidence is limited to the CVE record and public GitHub reports. No affected CPEs, vendor advisory, patch reference, or exploitation confirmation appears in the supplied bundle. Validate locally before declaring exposure or closure.

Mitigation direction

  • Identify any deployments of Online Banking System v1.0 or derived code.
  • Restrict access to administrative customer-management routes until fixed.
  • Review vendor or project guidance for an official patch or corrected release.
  • Replace unsafe SQL construction with parameterized queries and strict input validation.
  • Back up and review banking data for unexpected customer deletion or modification activity.

Validation and detection

  • Inventory applications exposing /net-banking/delete_customer.php.
  • Review code handling cust_id for parameterized database access.
  • Check web and database logs for unusual requests involving cust_id.
  • Run authorized non-destructive SQL injection testing in a controlled environment.
  • Confirm no public production route exposes vulnerable customer deletion behavior.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2022-40117 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-40117Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.