CVE-2026-62458 in Work in Process
Summary
by MITRE • 08/19/2026
Vulnerability in the Oracle Work in Process product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Work in Process. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Work in Process as well as unauthorized update, insert or delete access to some of Oracle Work in Process accessible data. CVSS 3.1 Base Score 7.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H).
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 08/19/2026
The identified vulnerability resides within the Oracle Work in Process component of Oracle E-Business Suite, specifically affecting internal operations across supported versions ranging from 12.2.3 to 12.2.15. This security flaw represents a significant risk to organizations relying on this enterprise resource planning software for manufacturing and production management workflows. The vulnerability is characterized by its ease of exploitation, requiring only low-privileged access and network connectivity via the HTTP protocol. An attacker does not need user interaction or complex social engineering tactics to initiate an attack vector, making it particularly dangerous in environments where internal users have standard operational privileges but limited administrative rights.
From a technical perspective, the flaw allows for two distinct categories of malicious outcomes: denial of service and data integrity compromise. The availability impact is severe, as successful exploitation can lead to complete system crashes or frequent hangs within the Oracle Work in Process application. This type of instability disrupts critical business operations, preventing users from accessing essential manufacturing data and halting production tracking processes. Simultaneously, the vulnerability grants unauthorized actors the ability to perform update, insert, or delete operations on accessible data fields. This integrity breach means that an attacker could alter work order statuses, modify inventory records, or corrupt production schedules without authorization, leading to potential financial loss and operational chaos.
The severity of this issue is quantified by a CVSS 3.1 Base Score of 7.1, which classifies it as High Severity. The vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H) highlights that while confidentiality remains unaffected, the impacts on integrity and availability are substantial. In terms of industry-standard classification frameworks, this vulnerability aligns with CWE-20 Improper Input Validation or CWE-436 Interpretation Conflict if the issue stems from parsing errors in HTTP requests. Furthermore, the exploitation technique maps to MITRE ATT&CK techniques such as T1595 Active Scanning for network reconnaissance followed by T1498 Network Denial of Service and potentially T1078 Valid Accounts if the attacker leverages compromised low-privileged credentials. The lack of user interaction requirement further elevates the risk profile, allowing for automated exploitation tools to target vulnerable instances efficiently.
To mitigate this vulnerability, organizations must prioritize applying the latest security patches provided by Oracle immediately. Since the affected versions are specific (12.2.3 through 12.2.15), administrators should verify their current patch level and apply the relevant CPU or PSU updates that address these internal operations flaws. In addition to patching, implementing network segmentation is crucial; restricting HTTP access to the Oracle E-Business Suite environment to only trusted IP ranges can reduce the attack surface for low-privileged attackers who might otherwise gain initial foothold through other means. Deploying Web Application Firewalls with rules designed to detect anomalous HTTP request patterns associated with denial-of-service attempts or unauthorized data manipulation can provide an additional layer of defense. Regular monitoring of application logs for signs of repeated crashes or unexpected database modifications will also aid in early detection and response to potential exploitation attempts.