CVE-2025-9559
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 8.7.5 to Infinity 24.2.2 are affected by a Insecure Direct Object Reference issue in a user interface component that can only be used to read data.
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 confidenceInsecure Direct Object Reference (IDOR) vulnerability in Pega Platform's user interface component allows unauthorized users to read data through direct object references without proper authorization validation. Affects versions 8.7.5 through Infinity 24.2.2.
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.1.0, < 23.1.5>= 24.1.0, <= 24.1.3>= 24.2.0, <= 24.2.2CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Pega Platform versionAccess the Pega Admin console or check the pr_engineering.xml/timestamp file in the Pega installation directory. Run 'System: Management > Application > PegaRULES' to retrieve the version from the Pega 7 platform or check About Pega from the hamburger menu in Infinity versions.Affected if Installed version is 8.7.5 through Infinity 24.2.2, specifically matching >= 7.1.0 and < 23.1.5 OR >= 24.1.0 and <= 24.1.3 OR >= 24.2.0 and <= 24.2.2
-
Locate the affected UI componentIdentify UI components in the Pega application that handle data retrieval and display, particularly those using direct object references. Check application rules for data accessors that accept object ID parameters without validation.Affected if The UI component accepting object ID parameters is present and accessible without embedded authorization checks in the request flow
-
Verify authorization bypass is possibleAttempt to access data objects through direct reference IDs using an unauthorized or low-privilege user account. Inspect the request/response for the UI component's data fetch mechanism to confirm no permission validation occurs before returning data.Affected if Data objects are returned to unauthorized users when the direct object reference is provided, without checking whether the requesting user has permission to view that specific object
A user is affected if their Pega Platform version falls within the affected ranges AND the vulnerable UI component is accessible AND direct object references return data without permission checks.
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 · scoped23.1.5
Implement proper authorization checks on the affected UI component to validate user permissions before returning data objects. Upgrade to a patched version if available from Pega.
Pega Platform 23.1.5, 24.1.4, or 24.2.3 (or later stable release)
- 1. Identify your current Pega Platform version by checking the System Management - About Pega Platform page
- 2. Review the Pega Software Product Compatibility Guide to confirm upgrade paths between your current and target versions
- 3. Plan your upgrade following Pega's standard upgrade methodology: backup your system, test in a non-production environment, then upgrade production
- 4. After upgrading, verify that the IDOR vulnerability in the user interface component is remediated by testing authorized and unauthorized access scenarios
- 5. Confirm your upgraded version is >= 23.1.5 or >= 24.1.4 or >= 24.2.3 to ensure you are on a fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9559 — 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-9559 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