LiveActive security incident?Get immediate response
CVE Record

CVE-2022-39035: Smart eVision - Stored XSS

Smart eVision has insufficient filtering for special characters in the POST Data parameter in the specific function. An unauthenticated remote attacker can inject JavaScript to perform XSS (Stored Cross-Site Scripting) attack.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Smart eVision 2022.02.21 can store unsafe user-supplied content that later runs JavaScript in another user’s browser. This is a stored cross-site scripting issue. Business impact is mainly account/session exposure, misleading actions in the web app, and data viewed through the victim’s browser, not direct server takeover.

Executive priority

Treat this as a moderate web application risk. It is not reported as actively exploited in the supplied evidence, but unauthenticated stored XSS can become high-impact when administrators or sensitive users view attacker-controlled content.

Technical view

The CVE describes insufficient filtering of special characters in a POST Data parameter in a specific Smart eVision function. An unauthenticated remote attacker can inject JavaScript, with exploitation requiring a victim to view the stored content. CVSS 3.1 is 6.1 with low confidentiality and integrity impact and no availability impact.

Likely exposure

Exposure is limited to organizations running Smart eVision version 2022.02.21, especially if the affected web function is reachable from untrusted networks or unauthenticated users.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation. The issue is remotely reachable and unauthenticated, but user interaction is required because the stored script affects a later viewer.

Researcher notes

Evidence is narrow: the CVE record identifies CWE-79, Smart eVision 2022.02.21, an unauthenticated stored XSS vector, and CVSS 6.1. The supplied bundle does not provide parameter names, affected route details, proof of exploitation, or patch version information.

Mitigation direction

  • Check Smart eVision and TWCERT guidance for a fixed or supported version.
  • Restrict public access to the affected Smart eVision interface where feasible.
  • Apply web input filtering and output encoding controls where supported.
  • Monitor Smart eVision access logs for unusual POST activity.
  • Prioritize remediation for internet-facing or administrator-used deployments.

Validation and detection

  • Inventory Smart eVision deployments and confirm whether version 2022.02.21 is present.
  • Confirm whether the affected function is reachable without authentication.
  • Review application logs for suspicious stored-content submissions.
  • Test remediation in a controlled environment using non-executable XSS markers.
  • Verify users with privileged access cannot trigger stored script execution.
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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2022-39035 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
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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
2Source 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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2022-39035Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Smart eVision Information Technology Inc.Smart eVision2022.02.21Listed
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.