CVE-2025-2161
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 versions 7.2.1 to Infinity 24.2.1 are affected by an XSS issue with Mashup
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 confidencePega Platform versions 7.2.1 through 24.2.1 contain a Cross-Site Scripting (XSS) vulnerability in the Mashup component, allowing attackers to inject malicious scripts that execute in the context of other users' sessions.
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>= 7.2.1, < 8.5.5>= 23.1.0, < 23.1.4>= 24.1.0, < 24.1.2= 24.2.0CVSS 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 versionLocate the installed Pega Platform version through the system admin console, about Pega screen, or version.properties file in the installation directoryAffected if The version falls within any of these ranges: >= 7.2.1 and < 8.5.5, OR >= 23.1.0 and < 23.1.4, OR >= 24.1.0 and < 24.1.2, OR = 24.2.0
-
Confirm Mashup component is activeCheck if the Mashup/gadget functionality is enabled in the Pega Platform configuration, typically through the Mashup tab in the system settings or by searching for mashup-related data pages and agentsAffected if Mashup functionality is enabled, configured, or being used in any application within the platform
-
Verify Mashup web part usageInspect application definitions and any web mashup configurations for active Pega Mashup or SAR (Single Record) web part implementations that could accept user-supplied inputAffected if Any Mashup components or web parts are configured and accessible to users
Your environment is affected if the installed Pega Platform version is within the vulnerable ranges AND the Mashup component is enabled or used.
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 · scoped8.5.523.1.424.1.2
Apply vendor-provided patches or upgrade to a version beyond 24.2.1; alternatively, review and restrict Mashup functionality if not required.
Pega Platform 24.2.1 (or the appropriate fixed version for your branch: 8.5.5, 23.1.4, or 24.1.2)
- 1. Review current Pega Platform version by logging into the system and checking the version information in the About Pega dialog
- 2. Determine which version branch your current installation falls into (7.x, 23.1.x, 24.1.x, or 24.2.x)
- 3. For version 7.2.1 to 8.5.4: Plan upgrade path to Pega Platform 8.5.5 or later
- 4. For version 23.1.0 to 23.1.3: Plan upgrade path to Pega Platform 23.1.4 or later
- 5. For version 24.1.0 to 24.1.1: Plan upgrade path to Pega Platform 24.1.2 or later
- 6. For version 24.2.0: Plan upgrade path to Pega Platform 24.2.1 or later
- 7. Before upgrading, back up the current system including the database and any custom configurations
- 8. Review Pega upgrade documentation for your specific version migration path
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2161 — 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-2025-2161 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