dbcve.org
Applications Technology StackApplication · Oracle

CVE-2026-60670

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 →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Applications Technology Stack product of Oracle E-Business Suite (component: Client System Analyzer). Supported versions that are affected are 12.2.3-12.2.15. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Applications Technology Stack. Successful attacks of this vulnerability can result in takeover of Oracle Applications Technology Stack. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/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 · high confidence

Unauthenticated HTTP vulnerability in the Client System Analyzer component of Oracle E-Business Suite versions 12.2.3-12.2.15 allows remote attackers with network access to achieve complete system takeover (full confidentiality, integrity, and availability compromise). The 'difficult to exploit' characteristic indicates the attack requires specific conditions but achieves maximum impact if successful.

MitigationRestrict network access to the Client System Analyzer interface (ideally disable if unused), and apply Oracle's security patch when released. Alternatively, implement Web Application Firewall (WAF) rules to detect and block malicious requests targeting this component.

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
Applications Technology StackApplication
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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 Oracle E-Business Suite installation and version
    Locate the Oracle E-Business Suite installation directory (commonly $ORACLE_HOME/apps) and check the version file or use SQL query: SELECT release_name FROM apps.fnd_product_groups;
    Affected if Version is between 12.2.3 and 12.2.15 (inclusive)
  2. Verify Client System Analyzer component status
    Check if the Client System Analyzer (CSA) is installed and enabled. This may be found in Oracle Applications Manager (OAM) or via the context file under $INST_TOP/appl/admin. Look for entries containing 'csa' or 'ClientSystemAnalyzer'.
    Affected if Client System Analyzer component is present and enabled in the E-Business Suite environment
  3. Confirm Client System Analyzer network accessibility
    Check if the CSA listener is running and exposed to the network. Typically CSA runs on ports 8000-8010 or custom ports. Use 'netstat -an | grep -E "800[0-9]"' or check OAM to verify CSA endpoints are listening on external interfaces.
    Affected if Client System Analyzer is listening on a network-accessible interface (0.0.0.0 or non-loopback address)
  4. Review network access controls on CSA endpoints
    Examine Oracle WebLogic/Apache configuration files (httpd.conf, apps.conf) and any firewall rules to determine if the CSA URLs (/csa*, /OA_HTML/csa*) are exposed to untrusted networks.
    Affected if No IP-based access restrictions or authentication requirements are enforced on CSA endpoints

If the E-Business Suite version is 12.2.3 through 12.2.15 AND the Client System Analyzer is network-accessible without proper access controls, the environment is affected by this vulnerability.

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

Restrict network access to the Client System Analyzer interface (ideally disable if unused), and apply Oracle's security patch when released. Alternatively, implement Web Application Firewall (WAF) rules to detect and block malicious requests targeting this component.

Fix this in Applications Technology Stack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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