dbcve.org
Jd Edwards Enterpriseone Accounts PayableApplication · Oracle

CVE-2026-46891

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 Accounts Payable product of Oracle JD Edwards (component: Accounts Payable). 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 Accounts Payable. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all JD Edwards EnterpriseOne Accounts Payable accessible data as well as unauthorized access to critical data or complete access to all JD Edwards EnterpriseOne Accounts Payable accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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

SQL injection or authorization bypass vulnerability in Oracle JD Edwards EnterpriseOne Accounts Payable module version 9.2. Low-privileged attackers with network access via HTTP can exploit this to create, delete, or modify critical financial data, or gain unauthorized read access to sensitive accounts payable information. The high confidentiality and integrity impacts with no availability impact indicate data exfiltration and tampering capabilities.

MitigationApply the Oracle Critical Patch Update for CVE-2026-46891. Prior to production deployment, test thoroughly in non-production environments given the critical nature of financial data in the Accounts Payable module.

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 Accounts PayableApplication
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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Verify Oracle JD Edwards EnterpriseOne Accounts Payable is installed
    Check your system for the presence of Oracle JD Edwards EnterpriseOne components, specifically the Accounts Payable module. This is typically found on Oracle WebLogic or Oracle Application Server infrastructure hosting JD Edwards EnterpriseOne applications.
    Affected if The Accounts Payable component of JD Edwards EnterpriseOne is present in the environment
  2. Determine the installed version of JD Edwards EnterpriseOne Accounts Payable
    Access the JD Edwards EnterpriseOne Administration or About information through the EnterpriseOne menu, OR query the version through the JD Edwards EnterpriseOne server configuration, OR check the Oracle EnterpriseOne Installer details for the Accounts Payable module.
    Affected if The installed version is exactly 9.2 (verify against Oracle's official version listing)
  3. Confirm network accessibility of the Accounts Payable HTTP endpoint
    Review network firewall rules, WebLogic/Oracle HTTP Server configuration, and load balancer settings to determine if the Accounts Payable component is accessible over HTTP/HTTPS from the network. Check for exposed URLs typically containing /jde/ or /E1Menu/ paths related to Accounts Payable.
    Affected if The Accounts Payable interface is reachable via HTTP/HTTPS from network locations
  4. Review user account privileges for Accounts Payable access
    Query the JD Edwards EnterpriseOne Security Server or use the Security Administration tool to list users with access to the Accounts Payable module. Check for low-privileged accounts that should not have create, modify, or delete permissions on financial data.
    Affected if Low-privileged or standard user accounts exist with network access to the Accounts Payable module

Your environment is affected if Oracle JD Edwards EnterpriseOne Accounts Payable version 9.2 is installed and the HTTP interface is network-accessible to low-privileged users.

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 the Oracle Critical Patch Update for CVE-2026-46891. Prior to production deployment, test thoroughly in non-production environments given the critical nature of financial data in the Accounts Payable module.

Fix this in Jd Edwards Enterpriseone Accounts Payable Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing32.0 h
  • Review / QA12.0 h
68.0 hours of engineering $11,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46891 — 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-46891 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