Threats / Oracle / CVE-2024-21287
CVE-2024-21287
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Oracle Agile Product Lifecycle Management (PLM) vulnerability
Oracle Agile PLM contains an incorrect authorization flaw in the Process Extension SDK component, allowing unauthenticated file disclosure.
Verdict
Today item — known-exploited.
An authorization bypass in Oracle Agile PLM's Process Extension SDK permits unauthenticated attackers to access sensitive files without proper credentials, exposing confidential product lifecycle data.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-11-21).
Probability (EPSS)
EPSS 0.01496 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Oracle, Agile Product Lifecycle Management (PLM). Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-863 Incorrect Authorization — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that the Process Extension component lacks proper authorization checks.
Business
Sensitive product development files and intellectual property become accessible to unauthorized parties.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I send requests to the vulnerable endpoint without authentication credentials.
Business
Competitors or malicious actors gain access to proprietary design specifications and development roadmaps.
3
Lateral reach — past segmentation narrative 3
Attacker
I retrieve confidential files containing product plans, source code, or customer information.
Business
The organization faces regulatory compliance violations, loss of competitive advantage, and potential customer notification obligations.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05