dbcve.org
Content ManagerApplication · Oracle

CVE-2026-60691

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 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 Content Manager product of Oracle E-Business Suite (component: Internal Operations). 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 Content Manager. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Content Manager accessible data as well as unauthorized access to critical data or complete access to all Oracle Content Manager 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

HTTP-based vulnerability in Oracle Content Manager's Internal Operations component allows low-privileged attackers to gain unauthorized creation, deletion, or modification access to critical data, as well as unauthorized read access to all Oracle Content Manager data. The CVSS 8.1 score reflects high confidentiality and integrity impacts with no availability impact.

MitigationApply the Oracle Critical Patch Update (CPU) or security alert that addresses CVE-2026-60691 for Oracle E-Business Suite versions 12.2.3-12.2.15. As a defensive measure pending patch deployment, restrict network access to Oracle Content Manager endpoints and monitor for anomalous HTTP activity.

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
Content ManagerApplication
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. Identify Oracle E-Business Suite application version
    Query the FND_PRODUCT_GROUPS table via SQL*Plus: SELECT release_name FROM fnd_product_groups; or use Oracle Applications Manager (OAM) > Site Map > Application Statistics to view the version.
    Affected if The reported version falls within 12.2.3 through 12.2.15.
  2. Confirm Oracle Content Manager module is configured
    Check if the ICX (Oracle Content Manager) product is installed and enabled by querying: SELECT product_name, status FROM fnd_product_installations WHERE product_name LIKE '%ICX%'; or check through OAM > Oracle Content Manager > Site Administration.
    Affected if The ICX/Oracle Content Manager product shows status as 'Installed' or 'Enabled'.
  3. Verify Content Manager web entry points are exposed
    Inspect the Oracle E-Business Suite web tier configuration (typically in $IAS_ORACLE_HOME/Apache/Apache/conf or Oracle HTTP Server config) for active servlets under /OA_HTML/ or /content/ paths that route to ICX functionality.
    Affected if HTTP endpoints handling Internal Operations content management are accessible without additional authentication layers beyond basic EBS login.
  4. Check for applied patches related to CVE-2026-60691
    Run the Oracle AD Patch utility against the applied patches: adident lsf <patch_number> or query OPATCH: opatch lsinventory -_detail | grep -i '60691' to see if the specific CPU patch addressing this CVE is applied.
    Affected if No patch for CVE-2026-60691 appears in the patch inventory for the EBS instance.

The environment is affected if Oracle E-Business Suite versions 12.2.3-12.2.15 are running with Oracle Content Manager enabled and no corresponding CVE-2026-60691 patch has been applied.

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

Apply the Oracle Critical Patch Update (CPU) or security alert that addresses CVE-2026-60691 for Oracle E-Business Suite versions 12.2.3-12.2.15. As a defensive measure pending patch deployment, restrict network access to Oracle Content Manager endpoints and monitor for anomalous HTTP activity.

Fix this in Content Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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