CVE-2025-2160 [High] | XSS in Pega Platform

CVE-2025-2160 is rated Low Risk (36.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.22%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.36%	0.22%	-0.14%
2	2026-05-30	0.31%	0.36%	+0.05%
3	2026-05-23	—	0.31%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.36%

0.22%

-0.14%

2026-05-30

0.31%

0.36%

+0.05%

2026-05-23

—

0.31%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.1	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	2.8	5.2	[email protected]
6.1	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.8	2.7	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.1

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

2.8

5.2

[email protected]

6.1

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.8

2.7

[email protected]

Affected software / configurations for CVE-2025-2160

Vendor	Product	Version	Raw CPE
pega	pega_platform	>= 8.4.3, < 8.5.5	cpe:2.3:a:pega:pega_platform::::::::
pega	pega_platform	>= 23.1.0, < 23.1.4	cpe:2.3:a:pega:pega_platform::::::::
pega	pega_platform	>= 24.1.0, < 24.1.2	cpe:2.3:a:pega:pega_platform::::::::
pega	pega_platform	24.2.0	cpe:2.3:a:pega:pega_platform:24.2.0:::::::*

References for CVE-2025-2160

URL	Tags
https://support.pega.com/support-doc/pega-security-advisory-d25-vulnerability-remediation-note	Vendor Advisory

URL

CVE-2025-2160

Exploit prediction scoring system (EPSS) score for CVE-2025-2160

Common vulnerability scoring system (CVSS) metrics for CVE-2025-2160

Weakness enumeration for CVE-2025-2160

Affected software / configurations for CVE-2025-2160

References for CVE-2025-2160