CVE-2026-60675
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 · uneditedVulnerability in the Oracle Applications Framework product of Oracle E-Business Suite (component: Search Bean). 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 Applications Framework. Successful attacks of this vulnerability can result in takeover of Oracle Applications Framework. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · moderate confidenceA vulnerability in the Search Bean component of Oracle Applications Framework (E-Business Suite versions 12.2.3-12.2.15) allows a low-privileged authenticated attacker with network access via HTTP to achieve complete takeover of the Oracle Applications Framework, impacting confidentiality, integrity, and availability.
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>= 12.2.3, <= 12.2.15CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Applications Framework versionQuery the database table FND_PRODUCT_INSTALLATIONS or use the 'about Oracle Applications' page accessible via /OA_HTML/about.htm. Alternatively, query SELECT version FROM fnd_product_groups WHERE product_group_name = 'Oracle Applications Framework';Affected if version falls within 12.2.3 through 12.2.15 inclusive
-
Confirm Search Bean component is installedCheck if the Search Bean module exists by querying SELECT parameter_value FROM fnd_profile_options WHERE profile_option_name = 'FND_SEARCH_BEAN_ENABLED'; or by inspecting the Oracle Applications Framework patches applied.Affected if Search Bean is present and enabled in the environment
-
Verify HTTP accessibility of Applications FrameworkCheck if the OA_HTML directory is accessible via web server. Examine web server configuration files (httpd.conf or equivalent) and Oracle E-Business Suite context file for enabled listener ports. Test HTTP access to /OA_HTML/舞台上 routes.Affected if HTTP access is enabled and the Search Bean servlet is accessible over the network without additional authentication barriers
-
Review recent access logs for Search Bean endpointsExamine Apache/Oracle HTTP Server access logs (typically in $LOG_HOME or $INST_TOP/logs) for requests to /OA_HTML/search or similar Search Bean related URLs. Look for unusual patterns from low-privileged accounts.Affected if Requests to Search Bean endpoints are logged from network sources, indicating the attack surface is exposed
Your environment is affected if Oracle Applications Framework version is between 12.2.3 and 12.2.15 inclusive AND the Search Bean component is enabled and accessible via HTTP network access.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the relevant Oracle patch for Oracle Applications Framework when released. Until then, restrict network access to the affected Oracle E-Business Suite interfaces and monitor for suspicious search bean interactions.
- 1. Navigate to Oracle Support and search for CVE-2026-60675 or the Oracle Applications Framework Critical Patch Update for the applicable quarter.
- 2. Obtain the specific patch number (e.g., a CPU patch) that addresses this vulnerability for Oracle E-Business Suite 12.2.x.
- 3. Review the patch readme and pre-install requirements provided by Oracle.
- 4. Apply the patch in a non-production environment first to validate compatibility.
- 5. After successful testing in non-production, schedule a maintenance window and apply the patch to production.
- 6. Verify the patch was applied successfully by checking the Oracle Applications Framework version and running any post-installation verification scripts.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60675 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60675 in production — separate from our analysis above.
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.
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.
- 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