Jd Edwards Enterpriseone Human Resources ManagementApplication · Oracle

CVE-2026-60493

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 Human Resources Management product of Oracle JD Edwards (component: Human Resources). 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 Human Resources Management. Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne Human Resources Management. 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

Vulnerability in Oracle JD Edwards EnterpriseOne HR Management (v9.2) allows a low-privileged authenticated attacker with network access via HTTP to perform actions beyond their authorized scope, leading to complete system compromise with high impact across confidentiality, integrity, and availability.

MitigationApply Oracle's latest Critical Patch Update for JD Edwards. Until patch is available, implement network segmentation to restrict HR management interface access and deploy WAF rules to detect and block anomalous HTTP requests.

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 Human Resources ManagementApplication
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 installation
    Locate the JD Edwards EnterpriseOne installation directory and identify the JD Edwards EnterpriseOne HR Management component. Check system inventory or deployment documentation for presence of JD Edwards EnterpriseOne 9.2 with HR Management module.
    Affected if JD Edwards EnterpriseOne 9.2 with HR Management module is installed
  2. Verify HR Management module version
    Query the JD Edwards EnterpriseOne System Administration tooling or check the JD Edwards Deployment Package documentation to confirm the exact HR Management version installed. Compare against the 9.2 baseline.
    Affected if HR Management version is 9.2 or falls within the affected version range for this CVE
  3. Confirm HR Management HTTP interfaces are exposed
    Review web server or enterprise server configuration for JD Edwards. Check if HTTP listeners are enabled for HR Management paths (typically /hrms/ or /hr/ endpoints in the Oracle WebLogic or IBM HTTP Server configuration). Inspect web.xml and enterprise server configuration files.
    Affected if HTTP access to HR Management interfaces is enabled and reachable over network
  4. Check for unauthorized SQL execution or command injection artifacts
    Review database audit logs and JD Edwards security logs for SQL injection patterns (unusual WHERE clause manipulation, unexpected UNION SELECT statements, or OS command execution calls). Check for new or unexpected stored procedures, functions, or scheduled jobs in the HR Management database schema.
    Affected if Suspicious SQL patterns or command injection indicators exist in logs or database objects
  5. Review access control configuration for HR Management
    Examine JD Edwards EnterpriseOne security configuration (EnterpriseOne Security Server, Role definitions) to verify if HR Management functions are restricted to appropriate roles. Check if low-privileged users can access HR Management administrative functions.
    Affected if Low-privileged or unauthorized network-accessible users have access to vulnerable HR Management functions

Environment is affected if JD Edwards EnterpriseOne 9.2 with HR Management module is installed, HTTP interfaces are exposed to network, and the system has not received Oracle's security patch for this CVE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's latest Critical Patch Update for JD Edwards. Until patch is available, implement network segmentation to restrict HR management interface access and deploy WAF rules to detect and block anomalous HTTP requests.

Recommended fix Moderate confidence

JD Edwards EnterpriseOne 9.2 (apply latest Oracle Critical Patch Update for JD Edwards)

  1. 1. Navigate to Oracle's Critical Patch Updates and Security Alerts page at https://www.oracle.com/security-alerts/
  2. 2. Locate the security advisory for JD Edwards EnterpriseOne related to this vulnerability
  3. 3. Identify the specific patch bundle number and version for JD Edwards EnterpriseOne 9.2
  4. 4. Download and apply the recommended patch following Oracle's installation documentation
  5. 5. Verify the patch was applied successfully by checking the JD Edwards EnterpriseOne application version
  6. 6. Test critical Human Resources functionality to confirm normal operation
Caveat Review Oracle's patch readme for any pre-requisites or configuration changes required before applying

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

Fix this in Jd Edwards Enterpriseone Human Resources Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60493 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-60493 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