dbcve.org
Agile Product Lifecycle ManagementApplication · Oracle

CVE-2025-21560

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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: SDK-Software Development Kit). 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. 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 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

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

This is an information disclosure vulnerability in the Oracle Agile PLM Framework SDK component. A low-privileged attacker with network access via HTTP can exploit this to gain unauthorized access to critical data or complete access to all accessible data within the Oracle Agile PLM system. The high confidentiality impact with no integrity or availability impact suggests the vulnerability allows reading sensitive data without modification.

MitigationApply the Oracle security patch for CVE-2025-21560 to the Oracle Agile PLM Framework 9.3.6 installation. If no patch is available, restrict network access to the SDK endpoints and review user privilege assignments until a patch can be applied.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 and version
    Locate the Oracle Agile PLM installation directory and check the version manifest or About information. Common paths include the installation root directory or within the application server logs. Use the application's About or version information page if accessible.
    Affected if The installed version is exactly 9.3.6
  2. Confirm SDK component is present
    Check for the presence of the Oracle Agile PLM Framework SDK directories or JAR files within the installation. Look for SDK-related folders or libraries in the installation root.
    Affected if The SDK component is installed as part of the Oracle Agile PLM deployment
  3. Verify SDK endpoints are network-accessible
    Test network connectivity to common Oracle Agile SDK HTTP endpoints from a low-privileged network position. Check if the SDK servlet or service endpoints respond to HTTP requests.
    Affected if SDK endpoints are reachable over the network without authentication or with low-privileged credentials
  4. Review SDK access controls
    Examine the SDK configuration and user role assignments to determine if low-privileged users can access SDK endpoints. Check the SDK configuration files or admin settings for permission levels.
    Affected if Low-privileged or unauthenticated users can access sensitive data through the SDK interface

You are affected if Oracle Agile PLM version 9.3.6 is installed with the SDK component exposed to network access, allowing low-privileged users to retrieve sensitive data via HTTP requests to SDK endpoints.

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 the Oracle security patch for CVE-2025-21560 to the Oracle Agile PLM Framework 9.3.6 installation. If no patch is available, restrict network access to the SDK endpoints and review user privilege assignments until a patch can be applied.

Fix this in Agile Product Lifecycle Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21560 — 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-21560 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