dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2025-21512

MEDIUM · 6.1 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 9.2.9.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 require human interaction from a person other than the attacker and while the vulnerability is in JD Edwards EnterpriseOne Tools, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of JD Edwards EnterpriseOne Tools accessible data as well as unauthorized read access to a subset of JD Edwards EnterpriseOne Tools accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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

JD Edwards EnterpriseOne Tools Web Runtime SEC component contains a vulnerability exploitable via HTTP that allows unauthenticated remote attackers to perform unauthorized read, insert, update, and delete operations on application data. The attack requires human interaction and results in a scope change affecting additional products.

MitigationApply Oracle JD Edwards EnterpriseOne Tools version 9.2.9.0 or later. If immediate patching is not possible, restrict network access to the Web Runtime interfaces and implement additional input validation at perimeter controls.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installation
    Locate the EnterpriseOne Tools installation directory, typically found under the path $JDE_HOME/system or C:\JDEdwards\E900\system. Check for the presence of the 'jdeenv.csh' (Unix) or 'jdeenv.bat' (Windows) initialization scripts, or look for the 'WEB-INF' directory under the web application server deployment folder.
    Affected if The product is not installed or the installation directories cannot be located.
  2. Determine the installed EnterpriseOne Tools version
    Open the jde.ini orjdemon.ini configuration file located in the $JDE_HOME/system/xx directory (where xx is the release such as '900'). Locate the 'Version=' entry under the [DEFAULTS] section. Alternatively, access the EnterpriseOne Diagnostic Workbench or the Server Manager console to view the installed Tools release version.
    Affected if The reported version number is lower than 9.2.9.0 (for example, 9.2.8.x, 9.2.7.x, or earlier).
  3. Verify if Web Runtime component is deployed and active
    Inspect the application server (Oracle WebLogic, IBM WebSphere, or Apache Tomcat) deployment configuration. Look for a deployed application named 'web' or 'WebRuntime' within the EnterpriseOne domain. Check the web.xml deployment descriptor for servlet mappings related to the SEC component. In the admin console, confirm the Web Runtime application state is 'Running'.
    Affected if The Web Runtime application is deployed and running on the application server.
  4. Check network accessibility of Web Runtime interfaces
    From an external host, attempt to reach the Web Runtime endpoints using a web browser or curl command. Common URLs follow the pattern http://<server>:8080/jde/web or https://<server>:8443/jde/web. Verify whether the network perimeter allows inbound HTTP/HTTPS traffic to the port used by the web application server.
    Affected if The Web Runtime URLs are reachable from untrusted networks and do not require authentication to access.

Your environment is affected if JD Edwards EnterpriseOne Tools with a version below 9.2.9.0 is installed, the Web Runtime SEC component is deployed and running, and the Web Runtime interface is network-accessible without additional access controls.

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

Apply Oracle JD Edwards EnterpriseOne Tools version 9.2.9.0 or later. If immediate patching is not possible, restrict network access to the Web Runtime interfaces and implement additional input validation at perimeter controls.

Recommended fix High confidence

9.2.9.0

  1. Confirm current JD Edwards EnterpriseOne Tools version by checking the Oracle JD Edwards EnterpriseOne Deployment Console or World Processor
  2. Download JD Edwards EnterpriseOne Tools version 9.2.9.0 or later from Oracle Support (support.oracle.com)
  3. Review Oracle JD Edwards upgrade documentation and release notes for version 9.2.9.0
  4. Schedule maintenance window and notify users as human interaction is required for successful exploitation
  5. Apply upgrade in non-production environment first to validate compatibility
  6. Apply upgrade to production environment during scheduled maintenance window
  7. Verify the Web Runtime SEC component is properly updated and functioning
  8. Test for the absence of open redirect vulnerability by validating redirect parameters are properly validated or rejected
Caveat Oracle JDE tools upgrades may require coordination with application updates and can affect custom configurations; test thoroughly before production deployment

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