CVE-2024-21287VulnerabilityPublished 18 Nov 2024Updated 21 Oct 2025

CVE-2024-21287: Oracle Agile PLM Framework · Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to

Affects Oracle Agile PLM FrameworkSource CVE Database V5

Exploited in the wild · KEV due 12 Dec 2024 · 1% EPSS : apply the vendor's fix or mitigations to Oracle Agile PLM Framework now.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 12 Dec 2024 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 18 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 3 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by oracle
2023-12-0722:28Z, 347 days before disclosure
CVE published
on cve.org
2024-11-1821:39Z, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2024-11-21, 3 days after disclosure
KEV remediation due
US federal deadline
2024-12-12, 24 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Affected software

Product	Affected	Fixed in
Mavencom.oracle/agile-plm-framework`pkg:maven/com.oracle/agile-plm-framework`Other threats	Affected =9.3.6	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Vulnerability in the Oracle Agile PLM Framework product of Oracle Supply Chain (component: Software Development Kit, Process Extension). The supported version that is affected is 9.3.6. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Agile PLM Framework. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Agile PLM Framework accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Impact

The primary impact of CVE-2024-21287 is unauthorized disclosure of sensitive data managed within Oracle Agile PLM Framework. This can lead to significant intellectual property theft, exposure of proprietary product lifecycle information, and potential competitive disadvantage. Since the vulnerability allows complete access to all data accessible by the framework, attackers could harvest extensive confidential business information. The absence of integrity or availability impact means the system's data and operations remain intact but compromised in confidentiality. For organizations relying on Oracle Agile PLM for supply chain and product lifecycle management, this breach could disrupt trust, cause regulatory compliance issues (especially in industries with strict data protection requirements), and lead to financial losses. The ease of exploitation without authentication or user interaction increases the likelihood of attacks, especially in environments where the affected version is exposed to untrusted networks. The vulnerability could also be leveraged as a foothold for further attacks within the corporate network.

Mitigation

1. Immediate mitigation should focus on restricting network access to Oracle Agile PLM Framework instances, especially blocking HTTP access from untrusted or external networks using firewalls or network segmentation. 2. Monitor Oracle's official security advisories for patches or updates addressing CVE-2024-21287 and apply them promptly once available. 3. Implement strict access control policies and review existing permissions within the Oracle Agile PLM environment to minimize data exposure. 4. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious HTTP requests targeting the vulnerable components. 5. Conduct thorough logging and monitoring of Oracle Agile PLM access logs to identify unusual or unauthorized access attempts. 6. If patching is delayed, consider deploying temporary compensating controls such as disabling vulnerable components or limiting functionality that exposes the SDK or Process Extension interfaces. 7. Educate IT and security teams about the vulnerability to ensure rapid incident response if exploitation attempts are detected. 8. Perform regular vulnerability scans and penetration tests focusing on Oracle Agile PLM to detect potential exploitation.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 09:04 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats