dbcve.org
Information ExposureWeakness · CWE-200

CVE-2020-36850

HIGH · 8.7 CVSS v4.0 Published 2025-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An information disclosure vulnerability exits in Sitecore JSS React Sample Application 11.0.0 - 14.0.1 that may cause page content intended for one user to be shown to another user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An information disclosure vulnerability in Sitecore JSS React Sample Application versions 11.0.0 through 14.0.1 allows page content intended for one user to be exposed to another user. This appears to be a broken access control or caching issue where user-specific content is not properly isolated, potentially due to improper session handling or direct object reference problems.

MitigationUpgrade to Sitecore JSS React Sample Application version 14.0.2 or later. If upgrading is not immediately possible, review user session isolation and caching mechanisms in the application to ensure content is properly scoped to the authenticated user.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed JSS React Sample Application version
    Locate the package.json or version manifest file in your Sitecore JSS React Sample Application deployment and note the version number.
    Affected if The version is 11.0.0, 12.0.0, 13.0.0, or 14.0.1 (any version from 11.0.0 through 14.0.1).
  2. Verify caching configuration for user-specific content
    Review the application configuration files and code that handle caching of rendered pages or components. Look for cache settings that may apply globally rather than per-user.
    Affected if Caching is enabled and user-specific or personalized content is being cached without user-specific cache keys.
  3. Inspect session handling implementation
    Examine how user sessions are managed in the application, particularly around how authenticated user context is established and maintained across requests.
    Affected if Session handling does not properly isolate user contexts or allows cross-user content leakage.
  4. Check for personalized content rendering paths
    Identify endpoints or routes that render user-specific or restricted content and trace how the user context is validated and applied during rendering.
    Affected if The application renders personalized content without properly scoping it to the authenticated user.

You are affected if your Sitecore JSS React Sample Application version is between 11.0.0 and 14.0.1 AND the application serves personalized or user-specific content that could be cached or improperly isolated between users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Sitecore JSS React Sample Application version 14.0.2 or later. If upgrading is not immediately possible, review user session isolation and caching mechanisms in the application to ensure content is properly scoped to the authenticated user.

Recommended fix Moderate confidence

Obtain the fixed release from Sitecore support (check CVE-2020-36850 security bulletin for exact version)

  1. 1. Identify the exact version of Sitecore JSS React Sample Application currently deployed
  2. 2. Check Sitecore Official Support (support.sitecore.com) for the specific security bulletin related to CVE-2020-36850
  3. 3. Review the affected versions (11.0.0 - 14.0.1) and determine if your deployment is within this range
  4. 4. If affected, obtain the fixed release version from Sitecore's official security advisory
  5. 5. Follow Sitecore's standard upgrade procedure for JSS React Sample Application
  6. 6. After upgrading, verify that the information disclosure vulnerability is resolved by testing user-specific content isolation
Caveat Review Sitecore release notes for the fixed version to check for any breaking changes in the JSS React Sample Application

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-36850 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-36850 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data