LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38619: SmartVista SVFE2 v2.2.22 was discovered to contain a SQL injection vulnerability via the UserForm:j_id90 pa...

SmartVista SVFE2 v2.2.22 was discovered to contain a SQL injection vulnerability via the UserForm:j_id90 parameter at /SVFE2/pages/feegroups/mcc_group.jsf.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-38619 is a critical SQL injection reported in SmartVista SVFE2 v2.2.22. If reachable, it could let an unauthenticated attacker interfere with backend database data, including reading, changing, or disrupting sensitive payment-processing information. The provided sources do not name a vendor patch or workaround.

Executive priority

Treat this as urgent for any environment running SmartVista SVFE2 v2.2.22, especially payment or financial processing systems. The business risk is high because the CVSS profile indicates unauthenticated remote database impact. If the product is absent, priority can drop after documented confirmation.

Technical view

The CVE describes CWE-89 SQL injection in the UserForm:j_id90 parameter at /SVFE2/pages/feegroups/mcc_group.jsf in SmartVista SVFE2 v2.2.22. 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 most likely where SmartVista SVFE2 v2.2.22 is deployed and the named JSF fee-group/MCC-group page is reachable over a network. The CVE affected metadata lists vendor and product as n/a, so asset validation is essential.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. A public technical reference is listed, but the provided data does not establish exploitation in the wild, available weaponized tooling, or a confirmed patch.

Researcher notes

Evidence is sparse: the CVE names a parameter, path, version, CWE, CVSS vector, and one public reference, while affected CPE/vendor metadata is incomplete. Avoid broad product assumptions. Validate assets and remediation guidance from the vendor before declaring exposure closed.

Mitigation direction

  • Identify any SmartVista SVFE2 v2.2.22 deployments immediately.
  • Check the vendor or maintainer for confirmed patches or workarounds.
  • Restrict network access to the SVFE2 administrative interface where feasible.
  • Increase monitoring for database errors and unusual requests to the named path.
  • Prioritize remediation before any internet-facing exposure remains in service.

Validation and detection

  • Confirm whether SmartVista SVFE2 v2.2.22 exists in the environment.
  • Check whether /SVFE2/pages/feegroups/mcc_group.jsf is reachable.
  • Review application logs for suspicious requests involving UserForm:j_id90.
  • Verify mitigation status against vendor guidance, not assumptions.
  • Document exposed hosts, network paths, and compensating controls.
Prepared
Confidence
medium
Sources
3

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-38619 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
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

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.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-38619Attack 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

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
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
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.