dbcve.org
Jd Edwards Enterpriseone Crm FoundationApplication · Oracle

CVE-2026-60489

HIGH · 8.8 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 4 weeks old

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 CRM Foundation product of Oracle JD Edwards (component: CRM Foundation). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise JD Edwards EnterpriseOne CRM Foundation. Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne CRM Foundation. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

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

This is a high-severity vulnerability in Oracle JD Edwards EnterpriseOne CRM Foundation version 9.2. The flaw is exploitable via HTTP by low-privileged attackers, allowing complete system takeover with high impact to confidentiality, integrity, and availability. The easily exploitable nature and HTTP attack vector suggest it may be an authentication bypass, authorization flaw, or injection vulnerability in the web-facing CRM component.

MitigationApply Oracle's security patch when available; in the interim, restrict network access to CRM Foundation endpoints via firewall/WAF rules and implement additional authentication controls for low-privilege accounts.

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 Crm FoundationApplication
Affected:= 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 CRM Foundation installation
    Locate the JD Edwards EnterpriseOne installation directory and identify the CRM Foundation component version. Common paths include $JDE_HOME/CRM or check the installed packages via the EnterpriseOne Package Manager or Server Manager.
    Affected if The CRM Foundation component is present and version 9.2 is installed
  2. Verify the exact CRM Foundation version number
    Access the JD Edwards EnterpriseOne Server Manager or check the About information within the CRM Foundation module. Query the version information via the EnterpriseOne Service Console or check the installed manifest files for the CRM component.
    Affected if The installed version matches 9.2 exactly, indicating the affected version range
  3. Confirm HTTP network accessibility to CRM Foundation
    Review the JD Edwards EnterpriseOne web server configuration (Oracle WebLogic or IIS depending on deployment). Check the CRM Foundation endpoint exposure by examining the web.xml deployment descriptors and network listener configurations.
    Affected if HTTP listeners are enabled and the CRM Foundation is accessible over the network without additional authentication layers beyond basic credentials
  4. Check user privilege levels on the CRM system
    Review the JD Edwards EnterpriseOne User Role and Security configuration to determine if low-privileged users have network access to the CRM Foundation module. Examine the role assignments for the CRM web applications.
    Affected if Low-privileged users (non-administrator roles) can authenticate via HTTP to the CRM Foundation interface

A user is affected if JD Edwards EnterpriseOne CRM Foundation version 9.2 is installed with HTTP network access enabled and low-privileged users can reach the CRM Foundation component remotely.

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

Apply Oracle's security patch when available; in the interim, restrict network access to CRM Foundation endpoints via firewall/WAF rules and implement additional authentication controls for low-privilege accounts.

Fix this in Jd Edwards Enterpriseone Crm Foundation 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-2026-60489 — 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-2026-60489 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