LiveActive security incident?Get immediate response
CVE Record

CVE-2020-0927: 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-0930, CVE-2020-0933, 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-0927 is a SharePoint cross-site scripting issue. A user with some access could send a crafted request that causes script to run in another user's browser. Business impact is mainly account-context data exposure or unauthorized actions inside SharePoint, not server takeover.

Executive priority

Handle through normal vulnerability management with priority for exposed or sensitive SharePoint environments. This is not documented as actively exploited in the provided sources, but SharePoint often contains sensitive business data and user-trust workflows.

Technical view

Microsoft describes improper sanitization of a specially crafted web request in SharePoint. CVSS 3.1 is 5.4: network reachable, low attack complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact. CWE-79 applies.

Likely exposure

Exposure is limited to organizations running Microsoft SharePoint Enterprise Server 2016 or Microsoft SharePoint Server 2019. Internet-facing or broadly accessible SharePoint deployments have higher practical risk, but the source bundle does not identify specific builds or configurations.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation would require low privileges and user interaction, which reduces urgency compared with unauthenticated server-side flaws but still matters for sensitive collaboration portals.

Researcher notes

The evidence identifies affected products, CWE-79, and CVSS details, but does not include patch KBs, build numbers, exploit telemetry, or workaround specifics. CVE-2020-0927 is explicitly separate from several other 2020 SharePoint XSS CVEs.

Mitigation direction

  • Review Microsoft MSRC guidance for CVE-2020-0927.
  • Apply Microsoft-supported SharePoint updates if the advisory lists them.
  • Prioritize externally reachable or high-value SharePoint portals.
  • Limit SharePoint access to necessary users while remediation is pending.
  • Treat generic web filtering as supplemental, not a vendor fix.

Validation and detection

  • Inventory SharePoint Enterprise Server 2016 and SharePoint Server 2019 instances.
  • Compare installed SharePoint patch levels with Microsoft MSRC guidance.
  • Confirm whether affected SharePoint sites are internet-accessible.
  • Review vulnerability scanner findings for CVE-2020-0927.
  • Document compensating controls if vendor remediation is delayed.
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-2020-0927 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-0927Attack 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
Weakness

CWE details

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