dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2025-21510

HIGH · 7.5 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 9.2.9.0 or later.
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 JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Web Runtime SEC). Supported versions that are affected are Prior to 9.2.9.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Tools. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all JD Edwards EnterpriseOne Tools 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

A vulnerability in the Web Runtime SEC component of JD Edwards EnterpriseOne Tools allows unauthenticated remote attackers to gain unauthorized access to critical data via HTTP. The flaw is easily exploitable and affects all versions prior to 9.2.9.0, with high confidentiality impact but no integrity or availability impact.

MitigationUpgrade JD Edwards EnterpriseOne Tools to version 9.2.9.0 or later to remediate this vulnerability. If immediate patching is not feasible, restrict network access to the Web Runtime interfaces using network segmentation or a web application firewall.

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 ToolsApplication
Affected:< 9.2.9.0

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 JD Edwards EnterpriseOne Tools version
    Locate the installed version of JD Edwards EnterpriseOne Tools using Oracle system management interfaces, installation directories, or version reporting tools provided by Oracle. Common locations include the [[ORACLE_HOME]]/tools directory or enterprise management consoles.
    Affected if The installed version is lower than 9.2.9.0
  2. Verify Web Runtime SEC component is enabled
    Check the Web Runtime SEC component configuration in the JD Edwards EnterpriseOne deployment. This is typically managed through the Oracle WebLogic Server console, JD Edwards EnterpriseOne Administrator, or the SEC configuration files within the Web Runtime deployment.
    Affected if Web Runtime SEC component is actively configured and running in the environment
  3. Confirm HTTP exposure of Web Runtime
    Identify whether the Web Runtime SEC interface is accessible via HTTP. Check web server configuration (such as Oracle WebLogic or Oracle HTTP Server), load balancer settings, and firewall rules to determine if HTTP listeners are open and routing traffic to the Web Runtime SEC endpoint.
    Affected if The Web Runtime SEC component is reachable over HTTP (port 80/443) from the network without requiring authentication
  4. Check for unauthenticated access paths
    Review the Web Runtime SEC configuration for any unauthenticated or publicly accessible endpoints. Examine security policies, authentication settings, and access control lists associated with the Web Runtime SEC component.
    Affected if Unauthenticated HTTP access to Web Runtime SEC endpoints is permitted without requiring valid credentials

The environment is affected if JD Edwards EnterpriseOne Tools version is below 9.2.9.0 AND the Web Runtime SEC component is enabled and exposed via HTTP, allowing unauthenticated remote attackers to access critical data.

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.0 or later
Fixed in 9.2.9.0
Interim mitigation

Upgrade JD Edwards EnterpriseOne Tools to version 9.2.9.0 or later to remediate this vulnerability. If immediate patching is not feasible, restrict network access to the Web Runtime interfaces using network segmentation or a web application firewall.

Recommended fix Moderate confidence

9.2.9.0 or later

  1. Upgrade JD Edwards EnterpriseOne Tools to version 9.2.9.0 or later to resolve the Web Runtime SEC vulnerability
  2. After upgrading, verify that the JD Edwards EnterpriseOne Tools Web Runtime SEC component is functioning correctly
  3. Confirm that network access controls remain appropriately configured post-upgrade
Caveat Review Oracle JD Edwards EnterpriseOne Tools 9.2.9.0 release notes for any compatibility considerations or configuration changes

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

Fix this in Jd Edwards Enterpriseone Tools 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 the upgrade done

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-21510 — 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-21510 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