CVE-2023-50166
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 8.5.4 to 8.8.3 is affected by an XSS issue with an unauthenticated user and the redirect parameter.
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 confidenceCross-site scripting (XSS) vulnerability in Pega Platform versions 8.5.4 through 8.8.3 allows unauthenticated attackers to inject malicious scripts via the redirect parameter.
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.5.4, <= 8.8.3CVSS 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 Pega Platform versionAccess the Pega Platform administration console or check the installation manifest to determine the exact version number. Common methods include viewing the 'About Pega' page in the system or checking the installation logs.Affected if The installed version is >= 8.5.4 and <= 8.8.3
-
Verify web access to Pega PlatformConfirm that the Pega Platform web interface is accessible over the network. This vulnerability is exploitable by unauthenticated attackers, meaning the login page or public-facing endpoints are in scope.Affected if The web interface is exposed and reachable
-
Inspect redirect parameter handlingExamine the application's handling of the 'redirect' parameter in login or authentication flows. Check if the parameter value is reflected in responses without proper output encoding or validation.Affected if The redirect parameter accepts arbitrary input and reflects it unsanitized in the response
A system is affected if it runs Pega Platform version 8.5.4 through 8.8.3 with its web interface accessible, as the unauthenticated XSS via the redirect parameter can be exploited.
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 · scopedApply the vendor patch or upgrade Pega Platform to a version beyond 8.8.3 that includes the security fix for this XSS vulnerability.
Pega Platform 8.8.4 or later (recommended: latest 8.x LTS release)
- Identify the current Pega Platform version in use (check in Admin Studio or by querying the pr_engineering database table)
- Confirm the version falls within the affected range of 8.5.4 to 8.8.3
- Review release notes on support.pega.com for version 8.8.4 or later to confirm the XSS fix is included
- Schedule a maintenance window for the upgrade
- Back up the existing Pega Platform database and rules repository
- Follow Pega's standard upgrade documentation for your current version to target release 8.8.4 or latest supported 8.x release
- After upgrade, verify the redirect parameter is properly sanitized and no longer permits script injection
- Test that legitimate redirect functionality still works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50166 — 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-50166 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