dbcve.org
E Business SuiteApplication · Oracle

CVE-2026-46939

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 12.2.15 or later.
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 Oracle Configure to Order product of Oracle E-Business Suite (component: Supply to Order Workbench). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Configure to Order. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Configure to Order accessible data as well as unauthorized access to critical data or complete access to all Oracle Configure to Order 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 · high confidence

Vulnerability in Oracle Configure to Order's Supply to Order Workbench component allows low-privileged attackers with network access via HTTP to both modify (create/delete/update) and read critical data within the Oracle Configure to Order module, achieving high confidentiality and integrity impact.

MitigationApply the latest Oracle Critical Patch Update addressing this vulnerability and restrict network access to Oracle E-Business Suite HTTP interfaces to minimize attack surface.

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
E Business SuiteApplication
Affected:>= 12.2.3, <= 12.2.15

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. Confirm Oracle Configure to Order is installed
    Query the Oracle E-Business Suite application registry or use Oracle Application Manager to list installed modules and verify 'Oracle Configure to Order' is present in the environment.
    Affected if Oracle Configure to Order module is not present in the application registry, the system is not affected by this specific vulnerability.
  2. Check the installed Oracle Configure to Order version
    Use Oracle Application Manager or query the APPS.FND_PRODUCT_INSTALLATIONS table to retrieve the exact version number of Oracle Configure to Order. Compare against the affected range 12.2.3 through 12.2.15.
    Affected if The installed version falls within 12.2.3 to 12.2.15 inclusive, the environment is within the affected version range.
  3. Verify Supply to Order Workbench is accessible
    Log into Oracle E-Business Suite and navigate to the Configure to Order responsibility. Attempt to access the Supply to Order Workbench function or check the function definition in Oracle Application Framework for its enabled status.
    Affected if The Supply to Order Workbench function is enabled and accessible to users, the vulnerable component is present in the environment.
  4. Assess network exposure of E-Business Suite HTTP interfaces
    Review network configuration, firewall rules, or load balancer access lists to determine if Oracle E-Business Suite HTTP ports (typically 8000-8009 or 80/443) are exposed to untrusted or public networks.
    Affected if HTTP interfaces are accessible from untrusted networks without proper access restrictions, low-privileged attackers could potentially reach the vulnerable component.

The environment is affected if Oracle Configure to Order version 12.2.3-12.2.15 is installed, the Supply to Order Workbench is enabled, and the HTTP interface is network-accessible to low-privileged attackers.

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 a release after 12.2.15
Interim mitigation

Apply the latest Oracle Critical Patch Update addressing this vulnerability and restrict network access to Oracle E-Business Suite HTTP interfaces to minimize attack surface.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.16 or later (via Critical Patch Update)

  1. Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2026-46939 from Oracle's official patch repository
  2. Ensure you have a valid Oracle Support contract to access patches
  3. Before applying, take a full backup of the Oracle E-Business Suite environment including database and application tier
  4. Review Oracle's pre-install requirements for the CPU patch
  5. Apply the patch during a planned maintenance window following Oracle's standard E-Business Suite patch application procedures
  6. After applying, verify the patch was installed successfully using adPatch or similar utilities
  7. Test the Supply to Order Workbench functionality to confirm the fix works correctly
Caveat Standard Oracle CPU patching risks apply - test thoroughly in non-production first; some patches may require additional steps or have dependencies

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

Fix this in E Business Suite Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing20.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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