dbcve.org
Agile Product Lifecycle ManagementApplication · Oracle

CVE-2025-21556

CRITICAL · 9.9 CVSS v3.1 Published 2025-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle Agile PLM Framework product of Oracle Supply Chain (component: Agile Integration Services). The supported version that is affected is 9.3.6. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Agile PLM Framework. While the vulnerability is in Oracle Agile PLM Framework, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Agile PLM Framework. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Critical authentication bypass or privilege escalation vulnerability in Oracle Agile PLM Framework's Agile Integration Services component (version 9.3.6). Allows low-privileged network attackers via HTTP to achieve complete system compromise (full confidentiality, integrity, and availability takeover). The scope change indicator suggests attacks may propagate to integrated downstream products.

MitigationApply Oracle's latest Security Patch Update for Oracle Agile PLM Framework immediately. Additionally, restrict network access to Agile Integration Services endpoints and implement additional authentication controls until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Agile Product Lifecycle ManagementApplication
Affected:= 9.3.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Agile PLM installation
    Locate Oracle Agile Product Lifecycle Management software on the system by checking common installation directories (e.g., $ORACLE_HOME, C:\Oracle\Agile, or /opt/oracle/agile) and look for Agile PLM executables or services
    Affected if Oracle Agile PLM software is present on the system
  2. Verify installed version
    Check the installed Agile PLM version by reviewing version files, about dialogs, or using the Agile admin console. Common locations include the install directory or registry entries for Windows installations
    Affected if The installed version is exactly 9.3.6
  3. Confirm Agile Integration Services is enabled
    Review the Agile PLM configuration to determine if the Agile Integration Services component is installed and active. Check for integration services processes, services, or web applications running under the Agile domain
    Affected if Agile Integration Services component is installed and running
  4. Assess network exposure of HTTP endpoints
    Identify network listeners bound to Agile Integration Services ports (typically ports 8080, 8443, or custom integration ports). Use netstat or similar tools to enumerate exposed HTTP/HTTPS endpoints
    Affected if Agile Integration Services HTTP endpoints are accessible from untrusted networks or the internet

A system is affected if Oracle Agile PLM version 9.3.6 is installed with the Agile Integration Services component enabled and exposed via HTTP, allowing unauthenticated or low-privileged network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's latest Security Patch Update for Oracle Agile PLM Framework immediately. Additionally, restrict network access to Agile Integration Services endpoints and implement additional authentication controls until patching is complete.

Fix this in Agile Product Lifecycle Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21556 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data