dbcve.org
PlatformApplication · Pega

CVE-2023-32088

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 ad-hoc case 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 ad-hoc case creation functionality allows attackers to inject malicious scripts, potentially compromising user sessions or stealing credentials. The vulnerability affects versions 8.1 through Infinity 23.1.0.

MitigationUpgrade to the patched version provided by Pega in their security bulletin, or apply the vendor-supplied patch for your specific version.

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. Verify Pega Platform is installed
    Access the Pega Platform admin interface or check system documentation to confirm Pega is deployed in your environment.
    Affected if Pega Platform is not present in your environment.
  2. Determine the installed Pega Platform version
    Log into the Pega admin console and navigate to the 'About Pega' page, or check the version information in your deployment documentation or installation logs.
    Affected if The installed version falls within 8.1.0 to 8.7.4 OR 8.8.0 to 8.2.
  3. Confirm ad-hoc case creation functionality is accessible
    Check if users have access to the case creation interface in Pega. This can be verified by reviewing user roles and permissions in the Access Manager or by confirming the case manager portal is in use.
    Affected if Ad-hoc case creation is enabled and accessible to users in your deployment.
  4. Review case type configuration for custom fields
    Examine any custom case types that allow ad-hoc field creation. Look for the specific case type rules related to ad-hoc case creation in the Pega Rule Explorer.
    Affected if Custom fields or dynamic case creation using user-supplied input is configured in your case types.

You are affected if Pega Platform versions 8.1.0 through 8.7.4 or 8.8.0 through 8.2 are running AND the ad-hoc case creation feature 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 8.7.5 / 8.8.3 or later
Fixed in 8.7.58.8.3
Interim mitigation

Upgrade to the patched version provided by Pega in their security bulletin, or apply the vendor-supplied patch for your specific version.

Recommended fix High confidence

Upgrade to Pega Platform 8.7.5 (for 8.1-8.7.x versions) or 8.8.3+ (for 8.8.x versions)

  1. 1. Identify the currently installed Pega Platform version using the System Management Application or by checking the pr_version table in the Pega database.
  2. 2. If running version >= 8.1.0 and < 8.7.5, plan upgrade to version 8.7.5 or later within the 8.x branch.
  3. 3. If running version >= 8.8.0 and < 8.8.3, plan upgrade to version 8.8.3 or later.
  4. 4. Review Pega upgrade documentation at support.pega.com for the specific upgrade path from your current version.
  5. 5. Perform a full backup of the Pega database and rules schema before upgrading.
  6. 6. Execute the upgrade following Pega's standard upgrade procedure, including running the upgrade scripts.
  7. 7. After upgrade, verify the ad-hoc case creation functionality works correctly and the XSS vulnerability is resolved.
Caveat Review Pega upgrade guide for any behavior changes between your current version and target version; test thoroughly in non-production environment first

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

Fix this in 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-2023-32088 — 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-32088 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