LiveActive security incident?Get immediate response
CVE Record

CVE-2020-0933: A cross-site-scripting (XSS) vulnerability exists when Microsoft SharePoint Server does not properly saniti...

A cross-site-scripting (XSS) vulnerability exists when Microsoft SharePoint Server does not properly sanitize a specially crafted web request to an affected SharePoint server, aka 'Microsoft Office SharePoint XSS Vulnerability'. This CVE ID is unique from CVE-2020-0923, CVE-2020-0924, CVE-2020-0925, CVE-2020-0926, CVE-2020-0927, CVE-2020-0930, CVE-2020-0954, CVE-2020-0973, CVE-2020-0978.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-0933 is a Microsoft SharePoint cross-site scripting issue. An attacker with low-level access could send a crafted request that, if a user interacts with it, may run script in that user's browser context. The likely business impact is limited data exposure or unauthorized actions, not service outage.

Executive priority

Treat as a moderate-priority SharePoint patching item. It is not known exploited from the provided sources, but exposed collaboration platforms should not carry known XSS flaws longer than normal patch windows.

Technical view

The flaw is CWE-79 XSS caused by improper sanitization of a specially crafted web request to affected SharePoint servers. CVSS 3.1 is 5.4: network reachable, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is most likely where Microsoft SharePoint Enterprise Server 2016, SharePoint Server 2019, or SharePoint Foundation 2013 SP1 remains deployed, especially if accessible to broad internal or external authenticated users.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. Exploitation is constrained by required low privileges and user interaction, but SharePoint's collaboration role can make user-targeted XSS operationally relevant.

Researcher notes

Do not assume unauthenticated compromise or server code execution. The CVSS vector indicates PR:L and UI:R, with browser-side confidentiality and integrity impact. Source evidence does not include payload details, exploit maturity, or a named workaround.

Mitigation direction

  • Review the Microsoft MSRC advisory for official updates or workarounds.
  • Prioritize remediation on internet-facing or partner-accessible SharePoint servers.
  • Reduce unnecessary SharePoint access until remediation is confirmed.
  • Apply least-privilege permissions for SharePoint users and groups.
  • Monitor Microsoft guidance for version-specific servicing requirements.

Validation and detection

  • Inventory SharePoint versions and identify 2016, 2019, or Foundation 2013 SP1 deployments.
  • Check each affected server against the Microsoft MSRC advisory status.
  • Confirm required SharePoint security updates are installed through approved patch records.
  • Review SharePoint and web logs for unusual crafted request patterns.
  • Validate no unsupported SharePoint instances remain externally reachable.
Prepared
Confidence
high
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-2020-0933 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
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
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-2020-0933Attack 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
MicrosoftMicrosoft SharePoint Enterprise Server2016Listed
MicrosoftMicrosoft SharePoint Server2019Listed
MicrosoftMicrosoft SharePoint Foundation2013 Service Pack 1Listed
Weakness

CWE details

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