dbcve.org
E Business SuiteApplication · Oracle

CVE-2024-21265

HIGH · 8.1 CVSS v3.1 Published 2024-10-15
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 Site Hub product of Oracle E-Business Suite (component: Site Hierarchy Flows). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Site Hub. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Site Hub accessible data as well as unauthorized access to critical data or complete access to all Oracle Site Hub 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

SQL injection or similar injection vulnerability in Oracle Site Hub's Site Hierarchy Flows component allows low-privileged attackers with network access via HTTP to create, modify, or delete critical data and gain unauthorized access to sensitive information. The low attack complexity and no user interaction requirement make it easily exploitable.

MitigationApply Oracle Critical Patch Updates for Oracle E-Business Suite 12.2.3-12.2.13 to address this vulnerability in the Site Hierarchy Flows 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
E Business SuiteApplication
Affected:>= 12.2.3, <= 12.2.13

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 installation and version
    Access the Oracle E-Business Suite About page via the Oracle Application Manager or query the FND_PRODUCT_GROUPS table to retrieve the release version (select release_name from fnd_product_groups).
    Affected if The installed version is 12.2.3 through 12.2.13 inclusive.
  2. Locate the Site Hierarchy Flows component
    Log into Oracle Application Manager and navigate to the Site Hub module administration area, or query the FND_APPLICATION and FND_RESPONSIBILITY tables to identify if the Site Hierarchy Flows component is registered in the instance.
    Affected if The Site Hierarchy Flows component is present and registered in the Oracle E-Business Suite instance.
  3. Verify Site Hierarchy Flows is accessible via HTTP
    Confirm that the Site Hub web interfaces are accessible through HTTP/HTTPS listeners by testing the relevant Oracle Application tier URLs (typically under /OA_HTML/ or /sitename/ paths for Site Hub).
    Affected if Network access to Site Hub interfaces is enabled and the component responds to HTTP requests.
  4. Check for low-privileged user access to Site Hierarchy Flows
    Review the responsibilities and roles assigned to low-privileged Oracle E-Business Suite users to determine if any standard or custom roles provide access to the Site Hierarchy Flows functionality.
    Affected if Low-privileged users (with basic or restricted responsibilities) have access to Site Hierarchy Flows functionality through assigned roles or responsibilities.

A user is affected if their Oracle E-Business Suite installation runs version 12.2.3 through 12.2.13 AND the Site Hierarchy Flows component is installed and accessible, allowing low-privileged attackers to exploit the injection flaw over 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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.13
Interim mitigation

Apply Oracle Critical Patch Updates for Oracle E-Business Suite 12.2.3-12.2.13 to address this vulnerability in the Site Hierarchy Flows component.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 (if available) or apply the relevant CPU patch for 12.2.13

  1. Check Oracle Support for the specific Critical Patch Update (CPU) containing the fix for CVE-2024-21265 by searching My Oracle Support for this CVE ID or the Site Hub component.
  2. Apply the relevant Oracle E-Business Suite security patch following Oracle's standard patching procedures (ADOP for R12.2 or ADPATCH for R12.1/12.0).
  3. After applying the patch, run the standard adoption tasks (apply, finalize, and cutover for R12.2).
  4. Verify the patch was successfully applied by checking the adpatch logs and confirming the Site Hub functionality works correctly.
  5. Apply the patch in a test environment first and conduct regression testing before applying to production.
Caveat Standard Oracle E-Business Suite patching risks apply - test thoroughly in non-production first as patches may affect dependent modules

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

Fix this in E Business Suite Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing20.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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