LiveActive security incident?Get immediate response
CVE Record

CVE-2022-26644: Online Banking System Protect v1.0 was discovered to contain multiple cross-site scripting (XSS) vulnerabil...

Online Banking System Protect v1.0 was discovered to contain multiple cross-site scripting (XSS) vulnerabilities via parameters on user profile, system_info and accounts management.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-26644 reports multiple cross-site scripting issues in Online Banking System Protect v1.0. If a vulnerable deployment exists, attackers may be able to run browser-side script in affected application areas. The public record does not provide CVSS, vendor ownership, patch status, or active exploitation evidence.

Executive priority

Treat this as a targeted application-risk item, not a confirmed widespread emergency. Prioritize quickly if the product handles real banking data or is internet-facing; otherwise validate presence first.

Technical view

The CVE description identifies XSS through parameters in user profile, system_info, and accounts management functions. The record does not specify reflected versus stored XSS, authentication requirements, affected roles, exact parameters, fixed versions, or CPEs.

Likely exposure

Exposure appears limited to organizations running Online Banking System Protect v1.0. The source bundle does not identify a vendor, package ecosystem, CPE, hosted service, or deployment prevalence, so asset discovery must confirm whether this software exists internally.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. A public GitHub reference exists, but the provided metadata is insufficient to characterize exploit maturity without reviewing beyond the bundle.

Researcher notes

Public metadata is sparse. The key unknowns are XSS type, affected parameters, authentication context, impact scope, and remediation availability. Avoid assuming exploitability beyond the listed application areas without direct validation.

Mitigation direction

  • Identify whether Online Banking System Protect v1.0 is deployed anywhere internally.
  • Check vendor or project guidance for fixed versions or official remediation.
  • Restrict access to administrative and account-management functions where feasible.
  • Review input validation and output encoding on affected profile, system_info, and account areas.
  • Prioritize replacement or compensating controls if no maintained patch exists.

Validation and detection

  • Inventory internet-facing and internal banking application assets for this product and version.
  • Review application routes for user profile, system_info, and accounts management exposure.
  • Confirm whether untrusted input is safely encoded before browser rendering.
  • Check logs for suspicious profile or account-management parameter activity.
  • Document whether authentication is required for each affected function.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

cve · low confidence lookup

CVE-2022-26644 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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