# CVE-2025-62183: Cross-site scripting in Pega Infinity

> An administrative user can inject malicious scripts into the Pega Platform UI, leading to low-impact confidentiality and integrity breaches.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Feb 2026
- **Updated:** 18 Feb 2026
- **Also known as:** GHSA-2mxv-4v56-9pp9

## What is CVE-2025-62183?

CVE-2025-62183 is a medium-severity cross-site scripting vulnerability in Pegasystems Pega Infinity, published on 17 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Pega Platform versions 8.1.0 through 25.1.1 are affected by a Stored Cross-site Scripting vulnerability in a user interface component.  Requires an administrative user and given extensive access rights, impact to Confidentiality and Integrity are low.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-62183?


## How do I fix CVE-2025-62183?

No fix has been published for CVE-2025-62183 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-62183 being exploited?

There is no known exploitation of CVE-2025-62183 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62183 and fix it if it is affected.

What it is: CVE-2025-62183 is a medium-severity cross-site scripting vulnerability in Pegasystems Pega Infinity, published on 17 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-62183 in the wild and no public exploit code.

Affected product: Pegasystems Pega Infinity. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62183/ (Markdown: https://insights.sbomify.com/CVE-2025-62183/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62183
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62183
- OSV: https://osv.dev/vulnerability/CVE-2025-62183

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62183/
Summaries are generated and may contain mistakes; the official description above is the record.