dbcve.org
E Business SuiteApplication · Oracle

CVE-2025-21516

HIGH · 8.1 CVSS v3.1 Published 2025-01-21
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 Customer Care product of Oracle E-Business Suite (component: Service Requests). Supported versions that are affected are 12.2.5-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Customer Care. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Customer Care accessible data as well as unauthorized access to critical data or complete access to all Oracle Customer Care 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 · moderate confidence

Vulnerability in Oracle E-Business Suite Customer Care Service Requests component allows low-privileged attackers with network access via HTTP to create, delete, or modify critical data and access sensitive information. The CVSS 8.1 score indicates high confidentiality and integrity impact with no availability impact.

MitigationApply Oracle Critical Patch Updates for Oracle E-Business Suite. Review Oracle's My Oracle Support notes for CVE-2025-21516 and verify the Customer Care Service Requests module is patched to a version beyond 12.2.13.

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 version
    Log into Oracle E-Business Suite as a system administrator and navigate to the 'About' page (typically at /OA_About/AboutOracleEBS.jsp), or query the FND_PRODUCT_INSTALLATIONS table for the APPL_TOP version information.
    Affected if The displayed version falls within the range >= 12.2.3 and <= 12.2.13.
  2. Verify Customer Care Service Requests module is enabled
    Log into Oracle E-Business Suite and check if the 'Customer Care' or 'Service Requests' responsibility is available. This can be done by navigating to the 'System Administrator' responsibility, then 'Security', 'User', 'Define' to see assigned responsibilities, or by checking if users have access to the Service Requests screens.
    Affected if The Service Requests module is accessible and assigned to any user responsibility in the system.
  3. Confirm patch level for CVE-2025-21516
    Query the Oracle database for applied patches related to this CVE, or check Oracle MetaLink/My Oracle Support for the specific patch number (July 2024 CPU or subsequent). Run the script: SELECT patch_name, patch_type FROM ad_bugs WHERE bug_number = '<CVE-2025-21516-patch-id>' or check the AD_APPLIED_PATCHES table.
    Affected if No patch specifically addressing CVE-2025-21516 has been applied, or the applied patch version is still within the 12.2.13 or earlier range.
  4. Check for unauthorized Service Request records
    Review the Service Requests tables (CS_SVC_REQUEST_ALL_B and related tables) for unexpected entries, or use the Service Requests workbench to audit recent create/modify actions performed by low-privileged users.
    Affected if Service Request records exist that were created, modified, or deleted by users without elevated privileges.

You are affected if your Oracle E-Business Suite version is between 12.2.3 and 12.2.13 inclusive AND the Customer Care Service Requests module is enabled and accessible to users in your environment.

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. Review Oracle's My Oracle Support notes for CVE-2025-21516 and verify the Customer Care Service Requests module is patched to a version beyond 12.2.13.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 (or latest 12.2.x release) - Oracle recommends staying within the 12.2.x family as the long-term stable release

  1. 1. Apply the January 2025 Oracle Critical Patch Update (CPU) which addresses CVE-2025-21516 for Oracle E-Business Suite.
  2. 2. Download the Oracle E-Business Suite patches from Oracle Support using the patch numbers listed in the January 2025 CPU for the Service Requests component.
  3. 3. Review Oracle Support Document 1969056.1 (E-Business Suite Patch Installation Guide) for detailed installation instructions specific to your EBS version.
  4. 4. Apply the patches in a test environment first to validate compatibility with your custom configurations.
  5. 5. After successful testing in non-production, schedule a maintenance window and apply the patches to production.
  6. 6. Verify the patches are applied correctly by checking the AD patch utilities and confirming the fix for CVE-2025-21516.
Caveat Standard Oracle EBS patch application carries standard risks - always test in non-production first; review Oracle's patch readme files for any version-specific considerations

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
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

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 locally
dbcve dependency scanner

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