PeopleSoft Enterprise PeopleTools EUVD-2026-105847

Exploitation requires (1) a valid low-privileged PeopleSoft Enterprise PeopleTools account (PR:L) with HTTP network access to the application, and (2) human interaction from a different user - i.e., a victim must be lured into interacting with attacker-supplied content via the Test Framework component (UI:R). It affects only PeopleTools versions 8.61 through 8.63. The scope-change nature (S:C) means a successful attack can cross a security boundary and impact additional products beyond PeopleTools. Limiting factors that reduce realistic risk: the attacker cannot act fully unauthenticated, and the attack cannot succeed without a second user's action, making targeted social-engineering or an active internal user base a practical prerequisite; there is no availability/denial-of-service impact.

This is a credible, high-priority vulnerability but not an emergency-patch-tonight scenario based on current signals. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 8.7) indicates a network-reachable, low-complexity flaw that nonetheless requires an authenticated low-privileged account (PR:L) and human interaction from a victim other than the attacker (UI:R), with a scope change (S:C) that lets the attack impact products beyond PeopleTools. The high score is driven primarily by the scope change plus high confidentiality and integrity impact; there is NO availability impact (A:N). No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The PR:L + UI:R requirements materially lower real-world risk versus a pure unauthenticated remote flaw: an attacker needs valid (even low-privilege) PeopleSoft credentials AND must lure a second user into interacting with their payload. CONFLICT TO NOTE: the input Tags include 'Authentication Bypass,' which contradicts the CVSS vector - PR:L means privileges ARE required, so this does not behave as an authentication bypass; treat that tag as suspect. Overall: a genuine high-severity issue worthy of prompt patching in the next maintenance window, especially given PeopleSoft's role as a system of record, but the authentication and user-interaction prerequisites argue against mass, automated exploitation.

An attacker with a low-privileged PeopleSoft account crafts a malicious payload within the Test Framework component and delivers it so that another user - likely a higher-privileged administrator or tester - interacts with it. When the victim triggers the content, the attack executes in a crossed privilege/security boundary (scope change), granting the attacker unauthorized read and write access to critical PeopleTools data and potentially adjacent products. No public exploit code was identified at time of analysis, and exploitation hinges on both valid credentials and victim interaction.