dbcve.org
Agile Product Lifecycle ManagementApplication · Oracle

CVE-2025-21565

HIGH · 7.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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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: Install). 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).

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

Unauthenticated information disclosure vulnerability in the Install component of Oracle Agile PLM Framework version 9.3.6. Attackers with network access via HTTP can gain unauthorized access to sensitive data without any credentials. The CVSS vector indicates high confidentiality impact with no integrity or availability impact.

MitigationRestrict network access to Install component endpoints until Oracle patch is available; ensure production deployments do not expose installation or configuration interfaces.

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

CVSS:3.1/AV:N/AC:L/PR:N/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
    Check for Oracle Agile PLM directories or services on the system. Common paths include $ORACLE_HOME/agile, or look for 'Agile' in installed services (Windows) or running processes.
    Affected if Oracle Agile PLM software is present on the system
  2. Verify installed version is 9.3.6
    Check version files or admin console. Common locations: <install_dir>/agile9.3.6/extensions or look for version.info in the Agile home directory. You can also query the admin interface if accessible.
    Affected if Installed version matches exactly 9.3.6
  3. Determine if Install component is exposed
    Check if HTTP/HTTPS ports used by the Install component are accessible. The Install component typically uses ports in the 8000-9000 range. Attempt a curl or HTTP request to common installation endpoints like /Install/ or /agile/Install/
    Affected if The Install component endpoints are reachable via HTTP from the network
  4. Check network accessibility of installation interfaces
    Review firewall rules, reverse proxy configurations, or load balancer settings that expose the /Install/ path. Scan accessible web endpoints for paths containing 'Install' or 'install'
    Affected if Installation or configuration interfaces are exposed to untrusted network segments
  5. Verify no authentication is required for Install endpoints
    Attempt to access Install component URLs without providing credentials. If data or configuration pages load without a login prompt, the vulnerability is present.
    Affected if Install component endpoints return sensitive data or configuration without requiring authentication

The environment is affected if Oracle Agile PLM version 9.3.6 is installed and the Install component is network-accessible without authentication.

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

Restrict network access to Install component endpoints until Oracle patch is available; ensure production deployments do not expose installation or configuration interfaces.

Fix this in Agile Product Lifecycle Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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