LiveActive security incident?Get immediate response
CVE Record

CVE-2021-30119: Authenticated Authenticated reflective XSS in Kaseya VSA <= v9.5.6

Authenticated reflective XSS in HelpDeskTab/rcResults.asp The parameter result of /HelpDeskTab/rcResults.asp is insecurely returned in the requested web page and can be used to perform a Cross Site Scripting attack Example request: `https://x.x.x.x/HelpDeskTab/rcResults.asp?result=<script>alert(document.cookie)</script>` The same is true for the parameter FileName of /done.asp Eaxmple request: `https://x.x.x.x/done.asp?FileName=";</script><script>alert(1);a="&PathData=&originalName=shell.aspx&FileSize=4388&TimeElapsed=00:00:00.078`

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-30119 is a medium-severity reflected cross-site scripting issue reported in Kaseya VSA up to v9.5.6. An authenticated user could cause script content to be reflected in a victim’s browser if the victim interacts with a crafted request. Business urgency is mainly for organizations still running affected VSA instances, especially internet-reachable management portals.

Executive priority

Prioritize remediation if Kaseya VSA remains in use, especially on exposed management portals. This is not presented as a critical unauthenticated takeover in the provided sources, but VSA is operationally sensitive software, so lingering exposure deserves prompt validation and cleanup.

Technical view

The source bundle describes authenticated reflected XSS in Kaseya VSA HelpDeskTab/rcResults.asp and done.asp request parameters. CVSS 3.1 is 5.4 with low complexity, low privileges required, user interaction required, changed scope, and low confidentiality/integrity impact. Structured affected-product data is incomplete, but the title identifies Kaseya VSA <= v9.5.6.

Likely exposure

Exposure is most likely where Kaseya VSA <= v9.5.6 is deployed and reachable by authenticated users. Risk increases if the VSA web interface is internet-accessible, broadly accessible internally, or used by privileged administrators whose browser sessions could be targeted.

Exploitation context

The source bundle does not provide evidence of active exploitation for this specific CVE, and KEV is false. The issue requires authentication and user interaction, so it is less direct than unauthenticated remote compromise but still relevant for phishing, helpdesk workflow abuse, or insider-adjacent scenarios.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, and DIVD references. The bundle names specific vulnerable pages and parameters but does not include CWE mapping, complete CPE data, exploit-in-the-wild confirmation, or a named fixed release. Avoid assuming broader Kaseya products are affected without vendor confirmation.

Mitigation direction

  • Identify any Kaseya VSA deployments and confirm their exact versions.
  • Review Kaseya and DIVD guidance for fixed versions or vendor-approved mitigations.
  • Restrict VSA web access to trusted administrative networks or VPN paths.
  • Reduce unnecessary authenticated access to the VSA web interface.
  • Monitor VSA web logs for unusual requests to the referenced paths.

Validation and detection

  • Confirm whether Kaseya VSA is present in asset inventory.
  • Check whether any instance is version 9.5.6 or earlier.
  • Verify whether VSA web access is internet-facing or broadly reachable internally.
  • Review access logs for suspicious requests involving the referenced vulnerable pages.
  • Use approved, non-destructive application testing to confirm remediation status.
Prepared
Confidence
medium
Sources
5

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-2021-30119 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-2021-30119Attack 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

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.