Customer SupportApplication · Oracle

CVE-2026-60844

HIGH · 8.1 CVSS v3.1 Published 2026-07-21
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 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 Customer Support product of Oracle E-Business Suite (component: Update Service Request). 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 Customer Support. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Customer Support accessible data as well as unauthorized access to critical data or complete access to all Oracle Customer Support 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

A high-severity vulnerability in Oracle E-Business Suite's Customer Support 'Update Service Request' component allows low-privileged remote attackers via HTTP to achieve unauthorized creation, deletion, or modification of critical data, as well as complete read access to sensitive Customer Support data. The attack requires no user interaction and exploits the lack of proper authorization controls in the service request update functionality.

MitigationApply the relevant Oracle Critical Patch Update for Oracle E-Business Suite version 12.2.3-12.2.15 immediately. If patching is not immediately feasible, restrict network access to the Customer Support module to trusted IPs and monitor for unauthorized service request modifications.

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
Customer SupportApplication
Affected:all versions

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 version
    Query the Oracle database version using SQL: SELECT version FROM fnd_product_groups; OR check the Oracle Applications Manager (OAM) interface for version information
    Affected if Version is 12.2.3 through 12.2.15 (inclusive) as these are the affected ranges per the CVE
  2. Confirm Customer Support module is enabled
    Navigate to Oracle E-Business Suite Responsibility menu: Customer Support > Service Requests. Verify the responsibility is available in the user's responsibility list
    Affected if Customer Support responsibility is assigned to any user profile, as this is the vulnerable component
  3. Verify HTTP-based form-based authentication is active
    Check Oracle E-Business Suite web listener configuration (Oracle HTTP Server or Apache) for enabled endpoints. Log in to the Customer Support responsibility via browser using standard form-based login
    Affected if HTTP/HTTPS access to Oracle E-Business Suite is enabled, since the attack vector is HTTP requests as stated in the summary
  4. Review Service Request modification logs for anomalies
    Query Oracle E-Business Suite audit tables: SELECT * FROM cs_incidents_all_b WHERE creation_date > SYSDATE-7; or check Oracle Middleware logging for unexpected SQL in service request update operations
    Affected if Unexpected or unauthorized service request creates, updates, or deletes are found in audit or application logs

You are affected if your Oracle E-Business Suite version falls between 12.2.3 and 12.2.15 and the Customer Support module is enabled and accessible via HTTP.

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 relevant Oracle Critical Patch Update for Oracle E-Business Suite version 12.2.3-12.2.15 immediately. If patching is not immediately feasible, restrict network access to the Customer Support module to trusted IPs and monitor for unauthorized service request modifications.

Fix this in Customer Support Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-60844 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