LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40115: 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_beneficiary.php.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-40115 is a critical SQL injection in Online Banking System v1.0. A vulnerable banking application could let an unauthenticated remote attacker affect database confidentiality, integrity, and availability through the customer ID handling described in the reports.

Executive priority

Prioritize quickly if this software or copied code exists in any banking workflow. The business risk is direct database compromise, but urgency depends on whether the application is actually deployed.

Technical view

The CVE describes CWE-89 SQL injection in the cust_id parameter of /net-banking/delete_beneficiary.php. CVSS 3.1 is 9.8 with network access, low complexity, no privileges, and no user interaction. The provided affected metadata is incomplete, listing vendor and product as n/a.

Likely exposure

Exposure is most likely in internet-facing or internal deployments of Online Banking System v1.0, forks, demos, or copied code. Asset matching is harder because the CVE record lacks vendor, product, CPE, and version metadata beyond the description.

Exploitation context

The bundle includes public vulnerability reports, but KEV is false and no cited source states active exploitation. Treat the issue as severe because the CVSS vector indicates unauthenticated network reachability and high database impact.

Researcher notes

The record is sparse: affected vendor/product data is n/a, and no official patch is named in the bundle. Research should focus on confirming code lineage, deployed route exposure, authentication assumptions, and whether downstream forks reused the vulnerable logic.

Mitigation direction

  • Identify any Online Banking System v1.0 deployments or derived code.
  • Check the project or vendor for updated guidance before applying changes.
  • If maintaining the code, replace unsafe SQL handling with parameterized queries.
  • Restrict public access until the vulnerable path is reviewed and corrected.
  • Back up and monitor banking databases for suspicious changes.

Validation and detection

  • Inventory web apps for Online Banking System v1.0 or forks.
  • Review cust_id handling in the beneficiary deletion route.
  • Confirm database calls use parameterized queries or equivalent safe APIs.
  • Run approved SAST or DAST checks in a non-production environment.
  • Verify logs for unexpected beneficiary deletion or database errors.
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-40115 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-40115Attack 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.