CVE-2025-62180: Pega Platform versions 8.3.0 through Infinity 25.1.2 are affected by an authorization weakness that may allow authenticated users to access certain additional data via crafted URLs.
Pega Platform versions 8.3.0 through Infinity 25.1.2 are affected by an authorization weakness that may allow authenticated users to access certain additional data via crafted URLs.
Security readout for executives and security teams
Plain-English summary
This issue lets a logged-in Pega user potentially view data they should not be authorized to see. It is not described as unauthenticated or actively exploited, but it matters because compromised accounts, customer users, or insiders could expose sensitive business data through authorization gaps.
Executive priority
Treat this as a high-priority data exposure risk, not a remote takeover. Prioritize affected Pega environments that expose sensitive records to broad authenticated populations, then follow Pegasystems remediation guidance.
Technical view
CVE-2025-62180 is a CWE-639 authorization weakness in Pega Platform/Pega Infinity versions 8.3.0 through Infinity 25.1.2. The CVSS 4.0 score is 7.1 high, with network access, low complexity, low privileges, no user interaction, high confidentiality impact, and low availability impact.
Likely exposure
Exposure is most likely in organizations running affected Pega Platform or Pega Infinity versions, especially portals with many authenticated internal, customer, or partner users. Systems holding regulated or customer data should be prioritized.
Exploitation context
The provided sources do not cite active exploitation, and the CVE is not marked KEV. Exploitation requires an authenticated user and crafted URLs, so risk rises with compromised credentials, broad user populations, or weak monitoring.
Researcher notes
Evidence is limited to the CVE record and referenced Pegasystems advisory pages. The issue maps to CWE-639, indicating object-level authorization weakness. Do not assume public exploit availability or exact patch mechanics beyond vendor guidance.
Mitigation direction
Check Pegasystems advisory I25 and H26 for the applicable remediation path.
Inventory all Pega Platform and Pega Infinity deployments and versions.
Prioritize remediation for internet-facing or customer-facing authenticated portals.
Review user access models for excessive data visibility.
Monitor Pega access logs for abnormal URL-based data access patterns.
Validation and detection
Confirm whether any deployment runs versions 8.3.0 through Infinity 25.1.2.
Map exposed Pega applications to data sensitivity and user populations.
Verify vendor remediation has been applied where applicable.
Review authorization tests for object-level access boundaries.
Check logs for unusual authenticated access before and after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.