Oracle Agile PLM CVE-2026-61166

Exploitation requires the attacker to already hold valid low-privileged credentials to the Oracle Agile PLM 9.3.6 application (CVSS PR:L, confirming authenticated access is mandatory) and network HTTP reachability to the application's web tier. The specific attack surface is the User and User Group component; no end-user interaction is needed (UI:N) and attack complexity is low (AC:L). Limiting factors that reduce real-world risk: an attacker cannot exploit this fully unauthenticated, exploitation is bounded to deployments still running the affected 9.3.6 version, and the Agile PLM management interface being exposed to the attacker's network is a prerequisite - instances reachable only from tightly segmented internal networks materially shrink the exposed population.

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 High) signals a genuinely serious, network-reachable flaw: no user interaction, low complexity, and only low privileges required, with a stated outcome of full 'takeover' of the product. The mitigating factor is PR:L - an attacker needs at least a valid low-privileged account, so this is not remote-unauthenticated mass-exploitation but rather a privilege-escalation risk from any authenticated foothold (insider, phished credentials, or a chained lower-tier vuln). No EPSS score, KEV listing, or public POC was provided, so real-world exploitation pressure appears currently low, but the low complexity and clean network vector mean weaponization could follow once patch-diffing of the July 2026 CPU occurs. Note a minor conflict: Oracle's own tag says 'Information Disclosure' while the CVSS impact and description assert full takeover (C/I/A all High) - the vector should be treated as authoritative and the tag as an incomplete label.

An attacker who has obtained any low-privileged Agile PLM account - via phishing, credential reuse, or an insider - sends crafted HTTP requests to the User and User Group component over the network. By abusing the flawed user/group handling, they escalate their permissions and pivot to full administrative control, taking over the entire Agile PLM instance and its product/supplier data. No public POC was identified at time of analysis, but the low attack complexity means reliable exploitation is plausible once technical details emerge.