Trading CommunityApplication · Oracle

CVE-2026-60784

HIGH · 8.1 CVSS v3.1 Published 2026-07-21

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 4 weeks old

Official description

NVD · unedited

Vulnerability in the Oracle Trading Community product of Oracle E-Business Suite (component: Party Search UI). 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 Trading Community. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Trading Community accessible data as well as unauthorized access to critical data or complete access to all Oracle Trading Community 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

dbcve analysis · high confidence

Vulnerability in Oracle E-Business Suite Trading Community's Party Search UI component allows low-privileged attackers with network access via HTTP to perform unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to critical or all accessible data. The CVSS vector indicates high confidentiality and high integrity impacts with no availability impact.

MitigationApply the latest Oracle Critical Patch Update (CPU) for Oracle E-Business Suite and restrict network access to the Party Search UI component to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Trading CommunityApplication

Affected:>= 12.2.3, <= 12.2.15

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Oracle E-Business Suite version

Connect to the database and run: SELECT version FROM apps.fnd_product_groups WHERE product_group_name = 'Oracle Application Object Library'; OR use the adident utility: $AD_TOP/bin/adident Header $AP_TOP/html/[filename]. This shows the installed 12.2.x version.

Affected if The version falls within >= 12.2.3 and <= 12.2.15
Confirm Trading Community module is installed

Query the database: SELECT application_name, application_id FROM fnd_application WHERE application_name LIKE '%Trading Community%'; OR check via Oracle Applications Manager (OAM) > Security > Installed Modules.

Affected if The Trading Community module (application_name contains 'Trading Community') is installed and enabled
Verify Party Search UI component is enabled

Check via Oracle Applications Manager: Navigate to Oracle E-Business Suite > Trading Community > Administration > Party Search UI. OR query: SELECT enabled_flag FROM hz_partystyle_lookups WHERE lookup_type = 'PARTY_SEARCH_UI_CONFIG';

Affected if The Party Search UI component shows as enabled or available in the web interface
Check network exposure of the web interface

Review Oracle E-Business Suite listener configuration (lsnrctl services) and web server (Apache/OHS) configuration for exposed endpoints. Check if the /oa_servlets/ or /oracle/ context paths for Trading Community are publicly accessible. Verify firewall rules and Oracle WebGate configuration.

Affected if The Party Search UI is accessible over network without restriction or VPN/IP filtering in place

A user is affected if they run Oracle Trading Community version 12.2.3 through 12.2.15 with the Party Search UI component enabled and exposed to network access, allowing low-privileged attackers to exploit the web interface.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.15

Interim mitigation

Apply the latest Oracle Critical Patch Update (CPU) for Oracle E-Business Suite and restrict network access to the Party Search UI component to trusted users only.

Recommended fix Moderate confidence

Apply the applicable Oracle E-Business Suite CPU patch (contact Oracle Support for specific patch number)

1. Log in to Oracle Support (support.oracle.com) and search for the CVE-2026-60784 security alert
2. Download the relevant Oracle E-Business Suite Critical Patch Update (CPU) that addresses this vulnerability for the Trading Community component
3. Review the patch readme and pre-install requirements specific to Oracle E-Business Suite 12.2.x
4. Apply the patch in a non-production environment first to validate compatibility
5. Schedule a maintenance window and apply the patch to production following Oracle's standard E-Business Suite patch application process
6. Verify the patch was applied successfully and test the Party Search UI functionality

Caveat Oracle E-Business Suite patches may require downtime and should be tested thoroughly in a staging environment before production deployment

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

Fix this in Trading Community 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 the upgrade done

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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-60784 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-60784?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 12.2.15 or later

Severity 8.1 High

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Trading Community

Remediation

A high-priority fix

Fix this in Trading Community 20 hrs · Moderate

Typical engagement from $3,500

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-60784 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References