LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40120: Online Banking System v1.0 was discovered to contain a SQL injection vulnerability via the search_term para...

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

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-40120 is a critical SQL injection in Online Banking System v1.0. A network attacker could potentially manipulate database queries through the transaction search function. The sources do not identify a vendor patch, commercial distribution, CPE, or active exploitation.

Executive priority

Treat as urgent only if this exact banking application or a fork is deployed. Critical CVSS reflects severe potential database impact, but the evidence base is narrow and does not show active exploitation.

Technical view

The reported flaw is CWE-89 SQL injection through the search_term parameter at /net-banking/customer_transactions.php. CVSS 3.1 is 9.8 with network access, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to deployments or forks of Online Banking System v1.0. The record lists no normalized vendor, product, versions, or CPEs, so asset matching requires codebase, route, and repository inventory.

Exploitation context

The CVE is not listed as KEV in the provided bundle. Public references describe the vulnerable parameter and route, but the bundle does not prove real-world exploitation, exploit maturity, or a vendor-supplied fix.

Researcher notes

Primary uncertainty is product identity. The CVE record lists affected vendor and product as n/a, while references point to a GitHub-hosted Online Banking System issue and report. Validate against actual code, not name matching alone.

Mitigation direction

  • Check the upstream repository and maintainer guidance for a fixed version or advisory.
  • Restrict public access to /net-banking/customer_transactions.php until remediation is confirmed.
  • For maintained forks, replace unsafe SQL construction with parameterized database queries.
  • Review database permissions used by the web application for least privilege.
  • Monitor application and database logs for suspicious search requests.

Validation and detection

  • Inventory whether Online Banking System v1.0 or forks are deployed.
  • Check whether /net-banking/customer_transactions.php is reachable in production.
  • Inspect handling of the search_term parameter in database query code.
  • Run authorized, non-destructive SQL injection testing in staging.
  • Review logs for unusual requests targeting the transaction search route.
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-40120 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-40120Attack 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.