LiveActive security incident?Get immediate response
CVE Record

CVE-2022-37028: ISAMS 22.2.3.2 is prone to stored Cross-site Scripting (XSS) attack on the title field for groups, allowing...

ISAMS 22.2.3.2 is prone to stored Cross-site Scripting (XSS) attack on the title field for groups, allowing an attacker to store a JavaScript payload that will be executed when another user uses the application.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-37028 is a stored cross-site scripting issue reported in ISAMS 22.2.3.2. A user with access to edit a group title could save script content that later runs in another user’s browser when the application displays it. The business risk is account-context abuse and data exposure within affected iSAMS sessions.

Executive priority

Treat this as a moderate-priority application security issue. It is not documented as actively exploited in the provided sources, but it can affect users who trust the iSAMS interface. Prioritize if iSAMS is used for sensitive school or organizational workflows.

Technical view

The issue is CWE-79 stored XSS in the group title field. CVSS 3.1 is 5.4, with network access, low complexity, low privileges, required user interaction, changed scope, low confidentiality impact, low integrity impact, and no availability impact. The structured affected-product metadata is incomplete, but the CVE text names ISAMS 22.2.3.2.

Likely exposure

Exposure is likely limited to organizations running the named ISAMS version and allowing users to create or edit group titles. Internet exposure matters less than authenticated application access, because exploitation requires low privileges and another user viewing the stored content.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The vulnerability is still operationally relevant because stored XSS can persist in normal application data and execute when higher-value users view affected pages.

Researcher notes

Evidence is concise: stored XSS in a group title field, CVSS 5.4, CWE-79, and no KEV flag. The bundle does not provide patch details, exploit telemetry, or complete CPE data, so validation should focus on confirming product version and vendor remediation status.

Mitigation direction

  • Check iSAMS and advisory sources for fixed versions or vendor guidance.
  • Upgrade or remediate according to the vendor’s published instructions.
  • Restrict group title editing to trusted roles until remediated.
  • Ensure group title output is safely encoded in all views.
  • Review logs for suspicious changes to group titles.

Validation and detection

  • Inventory iSAMS deployments and identify any 22.2.3.2 instances.
  • Review who can create or edit groups and group titles.
  • Confirm whether vendor guidance or updates have been applied.
  • In authorized testing, verify group titles render as inert text.
  • Check existing group titles for suspicious script-like content.
Prepared
Confidence
medium
Sources
5

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-37028 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
5.4 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
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-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.