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 access to the physical communication segment attached to the hardware where the 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. CVSS 3.1 Base Score 3.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N).

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "3.7",
  "pubDate": "2026-08-18T21:18:08.177Z",
  "pubdate": "2026-08-18T21:18:08.177Z",
  "executiveSummary": "A vulnerability has been identified within the Oracle Agile PLM MCAD Connector product of Oracle Supply Chain, specifically affecting the CAX Client component version 3.6. This security flaw introduces risks to both data confidentiality and data integrity within the targeted environment.\nThe vulnerability allows an unauthenticated attacker who has access to the physical communication segment attached to the hardware executing the Oracle Agile PLM MCAD Connector to compromise the application. Successful exploitation of this flaw does not allow for full system takeover, but it can result in unauthorized read access to a subset of accessible data, as well as unauthorized update, insert, or delete access to some of the accessible data.\nThe risk implications are moderate, reflected by a CVSS 3.1 Base Score of 3.7 with a vector of CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N. Exploitation is classified as difficult and features specific preconditions. Specifically, successful attacks require human interaction from an individual other than the attacker, alongside network positioning on the adjacent physical communication segment.\nOrganizations utilizing the affected Oracle Agile PLM MCAD Connector version 3.6 must account for these constraints when evaluating risk and prioritize defensive hardening strategies to limit physical segment access and mitigate potential human interaction vectors.",
  "technicalDetails": "The vulnerability resides in the CAX Client component of the Oracle Agile PLM MCAD Connector version 3.6. The architectural design of the affected component processes incoming communications or data streams in a manner that can be manipulated under specific network and user interaction conditions.\nRegarding network exposure and access requirements, the vulnerability operates via the Adjacent Network attack vector (AV:A). This means the attacker must have direct access to the physical communication segment attached to the hardware where the vulnerable Oracle Agile PLM MCAD Connector executes, precluding remote exploitation across wide-area networks without local segment presence. Furthermore, the attack complexity is rated as high (AC:H), indicating that successful exploitation requires specialized conditions, precise timing, or configuration nuances.\nAuthentication and privilege requirements are minimal for the threat actor, as the attack requires no prior authentication (PR:N) and no elevated privileges. However, the attack vector strictly mandates human interaction (UI:R) from a person other than the attacker. This implies that the victim must perform a specific action, such as interacting with a prompt, processing a crafted file, or engaging with the application interface, to facilitate the malicious sequence.\nThe attack flow proceeds as follows: First, the unauthenticated attacker establishes presence on the physical communication segment attached to the target hardware hosting the CAX Client component. Second, the attacker prepares and transmits the malicious payload or manipulation across the local communication medium. Third, leveraging the requirement for human interaction, the attacker induces the target user to perform an action that triggers the processing of the malicious input within the application context. Finally, upon successful processing, the vulnerability is triggered.\nThe post-exploitation impact is constrained to the application's data layer scope, manifesting as unauthorized read access to a subset of Oracle Agile PLM MCAD Connector accessible data, alongside unauthorized update, insert, or delete access to some accessible data. The Scope (S:U) remains unchanged, and availability (A:N) is unaffected, ensuring the service itself is not directly rendered unavailable by the exploit."
}