LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40121: Online Banking System v1.0 was discovered to contain a SQL injection vulnerability via the search parameter...

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

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-40121 is a critical SQL injection issue reported in Online Banking System v1.0. A vulnerable search field could let an unauthenticated remote attacker affect database confidentiality, integrity, and availability. Source metadata does not clearly identify a vendor, maintained product, patch, or supported version lineage.

Executive priority

Prioritize immediately if this banking application or derivative code is internet-facing or handles real customer data. The business risk is high because compromise could affect account records and service availability, while official remediation evidence is unclear.

Technical view

The CVE describes CWE-89 SQL injection in the search parameter of /net-banking/manage_customers.php. CVSS 3.1 is 9.8: network-accessible, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact. Affected product metadata is listed as n/a, limiting asset matching confidence.

Likely exposure

Exposure is most likely where Online Banking System v1.0, or code derived from the referenced GitHub project, is deployed and reachable over the network. The incomplete vendor and CPE data make automated scanner matching unreliable.

Exploitation context

The issue is publicly disclosed in CVE and GitHub references, but the source bundle does not show CISA KEV listing or confirmed active exploitation. Treat exploit availability details as incomplete unless validated from the cited public reports.

Researcher notes

The strongest evidence is the CVE record and linked GitHub reports. Weaknesses are sparse vendor identity, no CPEs, and no source-provided patch status. Validate against actual code provenance before broad conclusions about exposure.

Mitigation direction

  • Check the project or vendor source for any official fix or guidance.
  • Remove public exposure of affected deployments until remediation is confirmed.
  • Review the vulnerable search handling and use parameterized database queries.
  • Restrict access to customer-management routes behind strong authentication.
  • Monitor database and web logs for suspicious search activity.

Validation and detection

  • Inventory systems for Online Banking System v1.0 or derivative code.
  • Confirm whether /net-banking/manage_customers.php exists in deployed applications.
  • Review search-parameter database handling for unsafe query construction.
  • Run authorized SQL injection testing without using production data.
  • Verify remediation with regression tests for the customer search workflow.
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-40121 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-40121Attack 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.