CVE-2023-50167
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 from 7.1.7 to 23.1.1 is affected by an XSS issue with editing/rendering user html content.
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 confidenceCross-site scripting (XSS) vulnerability in Pega Platform versions 7.1.7 through 23.1.1 allows attackers to inject malicious scripts via user-supplied HTML content that is improperly sanitized during editing or rendering operations.
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>= 7.1.7, < 8.8.5= 23.1.1CVSS 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
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 your Pega Platform versionLocate the installed Pega Platform version in the system information, about page, or deployment documentation. Common locations include the Pega Infinity management console, system > sysmgmt > versioninfo, or the install directory properties files.Affected if The installed version falls within >= 7.1.7 and < 8.8.5, or equals exactly 23.1.1
-
Compare version against affected rangesVerify whether your version is vulnerable by checking if it matches the pattern: any version from 7.1.7 up to but not including 8.8.5, or version 23.1.1 specifically.Affected if Your version is 7.1.7, 7.2.x, 7.3.x, 8.x up to 8.8.4, or exactly 23.1.1
-
Determine if HTML content handling is in useAudit your Pega applications for any use of HTML input, rich text editors, or content management features that accept user-supplied HTML. Check rule forms, case types, or integrations that process HTML content from external sources.Affected if Your application accepts, stores, or renders user-supplied HTML content through Pega rules, portals, or integrations
-
Review HTML sanitization configurationInspect the Pega platform settings and any custom rules that handle output encoding or input validation for HTML content. Look for explicit sanitization of user-generated HTML in your application layer.Affected if No output encoding or input validation is configured for user-supplied HTML content being edited or rendered
You are affected if your Pega Platform version is 7.1.7 through 8.8.4, or exactly 23.1.1, and your system processes user-supplied HTML content through editing or rendering operations without proper sanitization.
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.8.5
Upgrade Pega Platform to version 23.1.2 or later which contains the security patch. If immediate upgrade is not feasible, implement output encoding and input validation on user-generated HTML content at the application layer as a compensating control.
Pega Platform 8.8.5 (or any version >8.8.5) or version >23.1.1
- Identify your current Pega Platform version by checking the System Management console or deployment artifacts
- Review your current deployment process and backup procedures for Pega Platform
- Plan maintenance window as upgrade will require system downtime
- Download Pega Platform 8.8.5 or later from Pega Marketplace or your licensed distribution channel
- Test the upgrade in a non-production environment first
- Execute upgrade following Pega's standard upgrade documentation for your migration path
- Verify the XSS vulnerability is resolved by testing user HTML content editing/rendering
- Deploy to production after successful validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50167 — 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-2023-50167 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