dbcve.org
Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2025-21511

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 · high confidence

Unauthenticated information disclosure vulnerability in JD Edwards EnterpriseOne Tools Web Runtime SEC component. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates a network-exploitable flaw with high confidentiality impact allowing remote attackers to access sensitive data without credentials.

MitigationApply Oracle Critical Patch Update or upgrade to JD Edwards EnterpriseOne Tools version 9.2.9.0 or later. Network segmentation and WAF rules may provide temporary mitigation until patching is possible.

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 installed JD Edwards EnterpriseOne Tools version
    Locate the Tools installation directory and check version information files, or use Oracle Enterprise Manager / JD Edwards Administration Console to retrieve the deployed Tools version
    Affected if version is lower than 9.2.9.0
  2. Confirm Web Runtime SEC component is enabled
    Review JD Edwards EnterpriseOne web configuration files (such as web.xml or jde.ini web settings) to verify the Web Runtime Security (SEC) component is present and active
    Affected if Web Runtime SEC component is installed and running
  3. Determine network exposure of the web interface
    Check network listening ports and firewall rules to verify if the JD Edwards web runtime ports (typically 80/443 or custom ports) are accessible from untrusted networks
    Affected if web interface is reachable over network without authentication
  4. Verify no authentication is required for the affected endpoint
    Test access to the Web Runtime SEC endpoints by sending unauthenticated HTTP requests to verify if sensitive information can be retrieved without credentials
    Affected if unauthenticated requests return sensitive data or system information

Environment is affected if JD Edwards EnterpriseOne Tools version is below 9.2.9.0 AND the Web Runtime SEC component is exposed and 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.

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

Apply Oracle Critical Patch Update or upgrade to JD Edwards EnterpriseOne Tools version 9.2.9.0 or later. Network segmentation and WAF rules may provide temporary mitigation until patching is possible.

Recommended fix High confidence

9.2.9.0

  1. Upgrade JD Edwards EnterpriseOne Tools to version 9.2.9.0 or later
  2. Verify the upgrade in a non-production environment before deploying to production
  3. After upgrading, confirm the Web Runtime SEC component is functioning correctly
  4. Test that the vulnerability is no longer exploitable

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