CVE-2020-8775
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 · uneditedPega Platform before version 8.2.6 is affected by a Stored Cross-Site Scripting (XSS) vulnerability in the comment tags.
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 · high confidencePega Platform before version 8.2.6 contains a stored XSS vulnerability in comment tags, allowing attackers to inject malicious JavaScript that executes in users' browsers when viewing comments. This stored XSS has high impact due to persistence and could lead to session hijacking, credential theft, or privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8.2.6CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Pega Platform versionLocate the version number by checking the Pega login page footer, or log into Pega Designer Studio and navigate to System > Settings > Version, or query the pr_engine_version database tableAffected if version is lower than 8.2.6 (e.g., 8.2.5, 8.2.4, 8.1.x, etc.)
-
Confirm comment/tag feature is enabledCheck if the Pega Platform has user-generated comment functionality active. This can be verified by examining application rules or checking if case comments are accessible to users in the applicationAffected if comment processing is active and the application allows users to create or view comments on cases or work items
-
Verify user-generated content handlingInspect whether the system accepts and stores user-supplied input in comment fields. This is typically enabled by default in standard Pega case management workflowsAffected if users can submit comments containing custom text or content that gets persisted and displayed to other users
The environment is affected if running Pega Platform version 8.2.5 or earlier AND the comment/tag feature is enabled, allowing stored XSS to be injected into comment fields and executed in other users browsers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.2.6
Upgrade Pega Platform to version 8.2.6 or later, or apply vendor-supplied patches for this specific XSS vulnerability in comment tag processing.
8.2.6
- Upgrade Pega Platform to version 8.2.6 or later to resolve the Stored XSS vulnerability in comment tags
- Consult official Pega upgrade documentation for your current version for detailed upgrade procedures
- Test the upgrade in a non-production environment before deploying to production
- After upgrade, verify that the comment tags functionality works correctly and the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-8775 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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