Description

Vulnerability in the Oracle Agile PLM MCAD Connector product of Oracle Supply Chain (component: CAX Client). The supported version that is affected is 3.6. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle Agile PLM MCAD Connector executes to compromise Oracle Agile PLM MCAD Connector. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Agile PLM MCAD Connector accessible data as well as unauthorized read access to a subset of Oracle Agile PLM MCAD Connector accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Agile PLM MCAD Connector. CVSS 3.1 Base Score 4.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L).

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "4.5",
  "pubDate": "2026-08-18T21:18:06.543Z",
  "pubdate": "2026-08-18T21:18:06.543Z",
  "executiveSummary": "A security vulnerability has been identified within the Oracle Agile PLM MCAD Connector product of Oracle Supply Chain, specifically within the CAX Client component. The affected supported version is 3.6. This vulnerability is classified as difficult to exploit, requiring specific preconditions for successful execution. The attack vector is localized, requiring an unauthenticated attacker to have prior logon access to the underlying infrastructure where the Oracle Agile PLM MCAD Connector executes. Furthermore, successful exploitation mandates human interaction from a user other than the attacker, adding a social or operational dependency to the attack chain.\nThe implications of a successful exploit span multiple security domains, impacting the confidentiality, integrity, and availability of the target application. Specifically, an adversary can achieve unauthorized read access to a subset of data accessible by the Oracle Agile PLM MCAD Connector, as well as unauthorized update, insert, or delete access to some of the accessible data. Additionally, successful attacks can cause a partial denial of service (partial DoS) of the Oracle Agile PLM MCAD Connector. The severity of this vulnerability is underscored by a CVSS 3.1 Base Score of 4.5, reflecting moderate risk due to the constrained attack vector, high attack complexity, and requirement for user interaction.",
  "technicalDetails": "The vulnerability resides in the CAX Client component of the Oracle Agile PLM MCAD Connector version 3.6. According to the CVSS 3.1 vector (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L), the attack vector (AV) is Local, meaning the threat actor must interact with the infrastructure hosting the target software locally or via an existing interactive session. The attack complexity (AC) is rated as High, indicating that the attacker must overcome significant procedural or environmental barriers, such as race conditions, precise timing, or complex payload staging, to successfully trigger the flaw.\nPrivileges required (PR) are None, implying that an unauthenticated user who has managed to provision or obtain logon access to the host environment can initiate the attack sequence. However, user interaction (UI) is Required, meaning the exploitation process cannot be fully automated from the attacker's initial foothold; it depends on another user performing a specific action—such as opening a maliciously crafted file, executing a compromised process, or interacting with a manipulated interface element—within the context of the vulnerable CAX Client component.\nThe step-by-step attack flow begins with the unauthenticated attacker securing logon access to the host infrastructure running Oracle Agile PLM MCAD Connector 3.6. The attacker then prepares a malicious payload or local state manipulation designed to target the CAX Client component. Because the attack complexity is high and requires specific conditions, the attacker must carefully orchestrate the local environment or wait for a secondary user to initiate a routine operational task. Upon execution and subsequent user interaction, the flawed component processes the tainted input or state insecurely.\nThe post-exploitation impact compromises core security tenets of the application data and runtime environment. The confidentiality impact (C:L) allows unauthorized read access to a subset of sensitive data accessible via the connector. The integrity impact (I:L) enables unauthorized write capabilities, specifically allowing the adversary to insert, update, or delete designated data records within the system's reach. Finally, the availability impact (A:L) results in a partial denial of service (partial DoS), degrading the operational performance or crashing specific functionalities of the Oracle Agile PLM MCAD Connector without causing a total system collapse. The scope (S:U) remains unchanged, limiting the impact strictly to the vulnerable component and its immediate data domain without directly breaching other distinct hypervisor or OS security domains."
}