dbcve.org
Pega PlatformApplication · Pega

CVE-2025-8681

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-10
Fix available
A fix is available. Upgrade to 23.1.5 / 24.1.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 7.1.0 to Infinity 24.2.2 are affected by a Stored XSS issue in a user interface component.  Requires a high privileged user with a developer role.

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

Stored XSS vulnerability in Pega Platform versions 7.1.0 through Infinity 24.2.2 allows a high-privileged user with developer role to inject malicious scripts into user interface components. These scripts persist and execute when other users interact with the compromised UI elements.

MitigationApply the vendor security patch for Pega Platform 24.2.2 or later. Until patched, limit developer role assignments to essential personnel only and audit UI component configurations for unauthorized modifications.

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:>= 7.1.0, < 23.1.5>= 24.1.0, < 24.1.3>= 24.2.0, < 24.2.2

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Pega Platform version
    Access the Pega Administrator portal or check the pr_engineering schema for the product version entry. Common locations include the 'pr_version' system table or the About Pega page in the admin console.
    Affected if The installed version falls within any of these ranges: >= 7.1.0 and < 23.1.5, OR >= 24.1.0 and < 24.1.3, OR >= 24.2.0 and < 24.2.2
  2. Review user role assignments for developer role
    Query the Pega security repository or access the User Management portal to list all users assigned the Developer role or equivalent high-privileged access.
    Affected if Any user account holds the developer role, particularly accounts accessible to non-administrative users or shared accounts
  3. Inspect UI component configurations for unauthorized script injection
    Review UI component definitions in Pega Studio or the UI Gallery. Examine property configurations, labels, and dynamic references for suspicious script tags or encoded payloads.
    Affected if Any user interface component contains script tags, event handlers, or encoded characters that were not authored by your development team
  4. Examine access and modification logs for developer role activity
    Review Pega audit logs focusing on the operator ID, access group, and role assignment changes. Filter for activities from developer role accounts within the UI component configuration areas.
    Affected if Audit logs show unexpected modifications to UI components made by developer role accounts, or unauthorized changes to role assignments themselves

Your environment is affected if the Pega Platform version is one of the affected versions listed AND any user possesses the developer role, as this combination enables the stored XSS attack vector.

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 23.1.5 / 24.1.3 / 24.2.2 or later
Fixed in 23.1.524.1.324.2.2
Interim mitigation

Apply the vendor security patch for Pega Platform 24.2.2 or later. Until patched, limit developer role assignments to essential personnel only and audit UI component configurations for unauthorized modifications.

Recommended fix High confidence

24.2.2 (or 23.1.5 for older branches)

  1. 1. Identify your current Pega Platform version from the System Management Console or logs.
  2. 2. Determine which version branch you are on (7.x to 22.x, 24.1.x, or 24.2.x).
  3. 3. For versions 7.1.0 to 22.x: Plan upgrade to Pega Platform 23.1.5 or later.
  4. 4. For version 24.1.0 to 24.1.2: Plan upgrade to Pega Platform 24.1.3 or later.
  5. 5. For version 24.2.0 to 24.2.1: Plan upgrade to Pega Platform 24.2.2 or later.
  6. 6. Review Pega upgrade guide and run pre-upgrade validation checks.
  7. 7. Perform upgrade in a non-production environment first.
  8. 8. Verify the upgrade was successful and test for regression.
Caveat Review Pega 23.1.5, 24.1.3, and 24.2.2 release notes for breaking changes and deprecated features before upgrading

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

Fix this in Pega Platform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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