dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-62180

HIGH · 7.1 CVSS v4.0 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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 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.

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

Pega Platform versions 8.3.0 through 25.1.2 contain a broken access control vulnerability where insufficient authorization checks allow authenticated users to access additional data beyond their intended permissions via crafted URLs. This is likely an Insecure Direct Object Reference (IDOR) issue where object-level authorization is not properly enforced on specific endpoints.

MitigationApply the vendor patch for CVE-2025-62180 to address the authorization weakness. Until patched, monitor access logs for suspicious URL patterns and review user role permissions to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Pega Platform installation and version
    Locate the Pega Platform installation and determine the installed version number. This is typically found in the system information, about page, or configuration files within the Pega installation directory.
    Affected if The installed version is 8.3.0 through 25.1.2 (inclusive)
  2. Confirm user authentication is enabled
    Verify that Pega Platform user authentication is active. Check if user accounts exist and the authentication mechanism (internal or external) is functioning.
    Affected if Users can authenticate to the platform, enabling the exploitation path described in the CVE
  3. Review access control configuration for the suspected endpoints
    Examine the Pega Platform access group and role configurations. Identify which endpoints or data objects may lack proper object-level authorization checks. Look for rules around pxCreateWork, pxRetrieve, or similar data access rules.
    Affected if Object-level authorization is not enforced on specific endpoints, allowing users to access data outside their intended permissions
  4. Inspect access logs for suspicious URL patterns
    Review Pega Platform access logs and web server logs for unusual or crafted URL requests that may indicate IDOR exploitation attempts. Look for patterns where object IDs or parameters are manipulated.
    Affected if Unusual access patterns or unauthorized data access attempts are observed in logs
  5. Audit user role assignments and data access permissions
    Review user role assignments and data access boundaries. Check if users have permissions that exceed what they should legitimately require for their job function.
    Affected if Users have overly broad permissions that could allow unauthorized data access through the vulnerable endpoints

A user is affected if Pega Platform version 8.3.0 through 25.1.2 is installed AND users can authenticate AND object-level authorization is not properly enforced on the relevant endpoints, allowing unauthorized data access via crafted URLs.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for CVE-2025-62180 to address the authorization weakness. Until patched, monitor access logs for suspicious URL patterns and review user role permissions to limit exposure.

Recommended fix Moderate confidence

Upgrade to Pega Infinity version 25.2 or later (contact Pega Support for exact fixed release)

  1. Contact Pega Support (support.pega.com) to obtain the specific security patch or hotfix for CVE-2025-62180
  2. Request documentation on the fixed version number and any prerequisites for applying the patch
  3. Review Pega's release notes for version Infinity 25.2 or later to confirm the vulnerability is addressed
  4. Schedule a maintenance window to test and apply the security update in a non-production environment first
  5. Apply the patch or upgrade to the confirmed fixed version in production after successful testing
  6. Verify the fix by testing that the authorization weakness is no longer exploitable via crafted URLs
Caveat Review release notes for any breaking changes between your current version and the target fixed version; test thoroughly in non-production first

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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