dbcve.org
PlatformApplication · Pega

CVE-2023-32087

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-18
Fix available
A fix is available. Upgrade to 8.7.5 / 8.8.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 versions 8.1 to Infinity 23.1.0 are affected by an XSS issue with task creation

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

Cross-site scripting (XSS) vulnerability in Pega Platform's task creation functionality allows attackers to inject malicious scripts that execute in the context of other users' sessions when tasks are viewed or interacted with.

MitigationUpgrade Pega Platform to version 23.1.1 or later which contains the security fix for this vulnerability.

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
PlatformApplication
Affected:>= 8.1.0, < 8.7.5>= 8.8.0, < 8.8.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 for Pega-related processes, services, or web applications running on the system. Look for Pega-specific directories, applications pools, or services in the environment.
    Affected if Pega Platform is installed and running
  2. Determine installed Pega Platform version
    Access the Pega Platform system and navigate to the About or System Information page, typically found in the system management console or by checking version information in the Pega logs or configuration files.
    Affected if Unable to retrieve version information from the system
  3. Compare version against affected ranges
    Match the installed version against the affected ranges: 8.1.0 through 8.7.4, or 8.8.0 through 8.8.2. These ranges indicate the system is vulnerable.
    Affected if Installed version falls within >= 8.1.0 and < 8.7.5, OR >= 8.8.0 and < 8.8.3
  4. Verify task creation functionality is accessible
    Confirm the Pega Platform web interface is accessible and the task creation feature is available to users. This is a standard feature in Pega Platform that would be present if the application is operational.
    Affected if Pega Platform is accessible and operational

If Pega Platform is installed and the version falls within 8.1.0 to 8.7.4 or 8.8.0 to 8.8.2, the environment is affected by this XSS vulnerability in the task creation functionality.

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 8.7.5 / 8.8.3 or later
Fixed in 8.7.58.8.3
Interim mitigation

Upgrade Pega Platform to version 23.1.1 or later which contains the security fix for this vulnerability.

Recommended fix Moderate confidence

Upgrade to Pega Platform 8.7.5+ (for 8.1-8.7.4 users) or 8.8.3+ (for 8.8.0-8.8.2 users); prefer latest LTS releases in each minor branch

  1. 1. Identify the current Pega Platform version by checking the system diagnostics or the 'About Pega' page
  2. 2. If running version >= 8.1.0 and < 8.7.5, upgrade to version 8.7.5 or later (recommended: latest 8.7.x LTS)
  3. 3. If running version >= 8.8.0 and < 8.8.3, upgrade to version 8.8.3 or later (recommended: latest 8.8.x release)
  4. 4. After upgrade, verify the XSS fix is included by reviewing the hotfix release notes in the upgrade package
  5. 5. Test task creation functionality to confirm the fix does not break existing workflows
  6. 6. Clear browser caches and test with multiple user roles to ensure XSS protection is functioning
Caveat Standard upgrade precautions apply: review release notes for behavior changes, test in non-production first, backup before upgrading

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

Fix this in Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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