dbcve.org
Pega PlatformApplication · Pega

CVE-2022-35654

MEDIUM · 6.1 CVSS v3.1 Published 2022-08-22
Fix available
A fix is available. Upgrade to after 8.7.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Pega Platform from 8.5.4 to 8.7.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 · high confidence

Pega Platform versions 8.5.4 through 8.7.3 contain a reflected Cross-Site Scripting (XSS) vulnerability in the redirect parameter that can be exploited by unauthenticated users, allowing attackers to inject malicious scripts via the URL.

MitigationUpgrade Pega Platform to a version beyond 8.7.3 that contains the security fix, or apply vendor-supplied patches to address the XSS vulnerability in 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
Pega PlatformApplication
Affected:>= 8.5.4, <= 8.7.3

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
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 checks

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

  1. Identify Pega Platform installation
    Check if Pega Platform is running in your environment by reviewing running web applications or checking for Pega-related processes/services
    Affected if Pega Platform software is present in your environment
  2. Determine the installed Pega Platform version
    Access the Pega Platform admin interface or system information page to retrieve the current version number
    Affected if The installed version is 8.5.4, 8.6.x, or 8.7.0 through 8.7.3
  3. Verify the affected version range
    Compare your installed version against the affected range: versions 8.5.4 through 8.7.3 are vulnerable
    Affected if The version falls within 8.5.4 <= version <= 8.7.3
  4. Check for exposed web interfaces
    Determine if unauthenticated web access to Pega Platform is possible by testing whether the login or redirect endpoints are reachable over the network
    Affected if The Pega Platform web interface is accessible to unauthenticated users and the redirect parameter can be manipulated

You are affected if Pega Platform version 8.5.4 through 8.7.3 is installed and the web interface with the redirect parameter is accessible to 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
Upgrade available Upgrade to a release after 8.7.3
Interim mitigation

Upgrade Pega Platform to a version beyond 8.7.3 that contains the security fix, or apply vendor-supplied patches to address the XSS vulnerability in the redirect parameter.

Recommended fix Moderate confidence

Pega Platform 8.8.1 or later (8.8.x branch)

  1. 1. Log in to the Pega Platform support portal (support.pega.com) and navigate to the Downloads or Patch section.
  2. 2. Locate and download Pega Platform version 8.8.1 or later (8.8.x releases contain the fix for CVE-2022-35654).
  3. 3. Review the 8.8.x release notes to confirm the XSS fix for the redirect parameter vulnerability is included.
  4. 4. Create a full backup of your current Pega Platform instance including the database and rules schema.
  5. 5. Set up a staging/test environment running the same version as production (8.5.4 to 8.7.3).
  6. 6. Perform the upgrade in the test environment first following Pega's standard upgrade procedure: stop services, run the upgrade script, verify database migration, restart services.
  7. 7. Validate that the redirect parameter XSS vulnerability is no longer exploitable by testing with a crafted redirect URL.
  8. 8. Once testing is complete and the fix is verified, schedule a maintenance window for production upgrade.
Caveat Review 8.8.x release notes for any deprecations or configuration changes that may affect your applications; some rules or functionalities may require updates after major version upgrades.

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

Fix this in Pega Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35654 — 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-2022-35654 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