dbcve.org
Product HubApplication · Oracle

CVE-2025-53043

HIGH · 8.1 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to after 12.2.14 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 Product Hub product of Oracle E-Business Suite (component: Item Catalog). Supported versions that are affected are 12.2.3-12.2.14. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Product Hub. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Product Hub accessible data as well as unauthorized access to critical data or complete access to all Oracle Product 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 the Item Catalog component of Oracle Product Hub (E-Business Suite 12.2.3-12.2.14). Low-privileged authenticated attackers can exploit this via crafted HTTP requests to achieve unauthorized data access (read) and modification (write/delete) operations on critical Oracle Product Hub data.

MitigationApply Oracle's latest Security Patch Update for Oracle E-Business Suite. Prior to production deployment, test thoroughly in a staging environment matching the production configuration.

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
Product HubApplication
Affected:>= 12.2.3, <= 12.2.14

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 FND_PRODUCT_INSTALLATIONS table via SQLPlus or SQL Developer connected as APPS user: SELECT product_version, patch_level FROM fnd_product_installations WHERE product LIKE '%Product Hub%'; Or access Oracle Applications Manager (OAM) to view system version information.
    Affected if The version is 12.2.3 through 12.2.14 inclusive, placing it within the affected range.
  2. Verify Product Hub module is installed
    Check if the Item Catalog component is accessible in the E-Business Suite. Log into the system with a standard user account and navigate to the Product Hub responsibility (typically under Catalog Management or Item Master). Confirm the module appears in the responsibilities menu.
    Affected if The Product Hub/Item Catalog module is present and accessible, indicating the vulnerable component exists in the environment.
  3. Confirm HTTP access to E-Business Suite web interfaces
    Verify the Oracle E-Business Suite web tier is running and accessible by attempting to reach the login page (typically at /OA_HTML/AppsLogin or /pls/<SID>). Check that the web listener is operational.
    Affected if HTTP access to the E-Business Suite is enabled and functional, as the attack vector requires crafted HTTP requests.
  4. Assess authentication configuration
    Confirm that low-privileged user accounts can be created or already exist in the system. Verify the Oracle E-Business Suite is configured to allow user authentication (not in a locked-down state preventing login).
    Affected if Low-privileged authenticated users can access the system, as the CVE requires a low-privileged authenticated attacker to exploit the vulnerability.

You are affected if your Oracle E-Business Suite version falls between 12.2.3 and 12.2.14, the Product Hub/Item Catalog module is installed, and the system accepts authenticated HTTP requests.

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.14
Interim mitigation

Apply Oracle's latest Security Patch Update for Oracle E-Business Suite. Prior to production deployment, test thoroughly in a staging environment matching the production configuration.

Fix this in Product Hub 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-2025-53043 — 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-2025-53043 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