dbcve.org
Jd Edwards Enterpriseone OrchestratorApplication · Oracle

CVE-2025-21552

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 9.2.9.2 or later.
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 JD Edwards EnterpriseOne Orchestrator product of Oracle JD Edwards (component: E1 IOT Orchestrator Security). Supported versions that are affected are Prior to 9.2.9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Orchestrator. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all JD Edwards EnterpriseOne Orchestrator 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 · high confidence

A vulnerability in the E1 IOT Orchestrator Security component of JD Edwards EnterpriseOne Orchestrator allows authenticated low-privilege attackers with network access via HTTP to read critical data or all accessible data in the system. The vulnerability has high confidentiality impact with no integrity or availability impact.

MitigationApply Oracle's patch (version 9.2.9.2 or later) from Oracle Critical Patch Updates to address this vulnerability in the JD Edwards EnterpriseOne Orchestrator.

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
Jd Edwards Enterpriseone OrchestratorApplication
Affected:< 9.2.9.2

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 if JD Edwards EnterpriseOne Orchestrator is installed
    Check your Oracle JD Edwards deployment documentation or look for the Orchestrator application server components in your environment. Common installation paths include $JDE_HOME/部署/Orchestrator or check Oracle Enterprise Manager for JD Edwards components.
    Affected if The Orchestrator component is present in the environment
  2. Determine the installed Orchestrator version
    Access the Orchestrator through its web interface (typically /jde/orchestrator or /iot), then navigate to System Administration > About or check the version information in the Oracle JD Edwards EnterpriseOne Lifecycle Management tools. Alternatively, query the database tables for version metadata (table JDE_ORCH_VERSION or similar).
    Affected if The installed version is lower than 9.2.9.2 (e.g., 9.2.8.x, 9.2.7.x, etc.)
  3. Verify the E1 IOT Orchestrator Security component is enabled
    Log into the JD Edwards EnterpriseOne Orchestrator and navigate to Security > IOT Security or check the Orchestrator configuration settings. This component handles data access and authorization for IoT-related orchestrator workflows.
    Affected if The E1 IOT Orchestrator Security component is configured and active in the deployment
  4. Confirm network accessibility of the Orchestrator HTTP endpoints
    Check if the Orchestrator web services are exposed on HTTP/HTTPS ports (typically 8080, 8443, or your configured web server ports). Review your load balancer, web server, or Oracle WebLogic configuration for URL mappings to /orchestrator or /iot paths.
    Affected if The Orchestrator is reachable over HTTP/HTTPS from the network where low-privilege users have access

A user is affected if JD Edwards EnterpriseOne Orchestrator is installed with version lower than 9.2.9.2, the E1 IOT Orchestrator Security component is enabled, and the HTTP interface is accessible to authenticated low-privilege users.

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.

dbcve · scoped
Upgrade available Upgrade to 9.2.9.2 or later
Fixed in 9.2.9.2
Interim mitigation

Apply Oracle's patch (version 9.2.9.2 or later) from Oracle Critical Patch Updates to address this vulnerability in the JD Edwards EnterpriseOne Orchestrator.

Recommended fix High confidence

9.2.9.2

  1. 1. Back up the JD Edwards EnterpriseOne Orchestrator database and configuration files.
  2. 2. Review the JD Edwards EnterpriseOne Orchestrator 9.2.9.2 release notes and prerequisites.
  3. 3. Download Oracle JD Edwards EnterpriseOne Orchestrator version 9.2.9.2 from Oracle's official distribution channels.
  4. 4. Stop the JD Edwards EnterpriseOne Orchestrator services.
  5. 5. Install version 9.2.9.2 following Oracle's standard upgrade documentation.
  6. 6. Verify the installation completed successfully.
  7. 7. Restart the Orchestrator services.
  8. 8. Validate that the E1 IOT Orchestrator Security component is functioning correctly.
Caveat Review Oracle's release notes for any configuration or compatibility changes in 9.2.9.2

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jd Edwards Enterpriseone Orchestrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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