CVE-2024-21287
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).
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. An authorization check is wrong. The attacker sends ordinary-looking requests, so a WAF has nothing to match on.
Also consider: patch · per-resource ACL
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-21287 being exploited?
Yes. CVE-2024-21287 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-21287?
CVE-2024-21287 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-21287?
Yes. A fix has been recorded for CVE-2024-21287. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-21287 affect?
CVE-2024-21287 affects oracle:agile_product_lifecycle_management. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected9.3.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- partial
Assessed by CISA 23 Nov 2024 (SSVC 2.0.3).
timeline
- 18 Nov 2024Published
- 21 Nov 2024Added to CISA KEV (exploited in the wild) · 2 days later
- 23 Nov 2024CISA SSVC assessment: exploitation active · 2 days later
- 12 Dec 2024CISA remediation due date (US federal agencies) · 19 days later
- 21 Oct 2025CVE record last updated · 314 days (about 10 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Advisoryoracle.com /security-alerts/alert-cve-2024-21287.html
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-21287
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.