dbcve.org
WorkflowApplication · Oracle

CVE-2025-53052

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to after 12.2.14 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Workflow product of Oracle E-Business Suite (component: Workflow Notification Mailer). Supported versions that are affected are 12.2.3-12.2.14. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Workflow. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Workflow, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Workflow accessible data as well as unauthorized read access to a subset of Oracle Workflow accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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

Unauthenticated HTTP vulnerability in Oracle Workflow Notification Mailer (E-Business Suite 12.2.3-12.2.14) allows remote attackers to read, insert, update, or delete a subset of Oracle Workflow data through a network attack requiring human interaction. The vulnerability is in the mailer component and can impact additional products due to scope change.

MitigationApply Oracle's latest security patches for Oracle E-Business Suite. Until patches are applied, restrict network access to the Workflow Notification Mailer interfaces and monitor for suspicious notification-related activity.

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
WorkflowApplication
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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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
    Run the Oracle AD_ident utility or query the FND_PRODUCT_GROUPS table to obtain the installed EBS version. Example SQL: SELECT release_name FROM fnd_product_groups;
    Affected if The version returned is between 12.2.3 and 12.2.14 inclusive, indicating the installation falls within the affected version range.
  2. Confirm Oracle Workflow component version
    Query the WF_VERSION view or check the workflow-related tables to verify the Workflow component version matches the EBS version. Example: SELECT text FROM wf_version WHERE name = 'WF';
    Affected if The workflow version is 12.2.3 through 12.2.14, indicating the vulnerable Workflow component is installed.
  3. Verify Workflow Notification Mailer is configured
    Check if the Workflow Notification Mailer is enabled by querying the WF_NOTIFICATION_OUT table or checking the mailer service status in Oracle Applications Manager. Look for active mailer configuration entries.
    Affected if The Notification Mailer component is enabled or configured, meaning the vulnerable mailer interface is active.
  4. Check HTTP accessibility of mailer interfaces
    Review the Oracle HTTP server configuration and network access controls to determine if the Workflow Notification Mailer servlet endpoints are exposed to network access. Check listener.ora and httpd.conf for mailer-related mappings.
    Affected if The mailer HTTP endpoints are accessible from the network without authentication, increasing exposure to the vulnerability.
  5. Audit for suspicious notification activity
    Review Oracle Audit tables and WF_NOTIFICATION_OUT for unexpected notification entries, especially bulk or automated-seeming notification creation/modification activity from unexpected sources.
    Affected if Unusual notification-related activity is observed in logs or audit trails, potentially indicating exploitation attempts.

A user is affected if they have Oracle E-Business Suite version 12.2.3-12.2.14 with the Workflow Notification Mailer component enabled and its HTTP interfaces network-accessible.

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

Apply Oracle's latest security patches for Oracle E-Business Suite. Until patches are applied, restrict network access to the Workflow Notification Mailer interfaces and monitor for suspicious notification-related activity.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.15 or later (verify with Oracle Support for exact fixed version)

  1. Check Oracle E-Business Suite supported version lifecycle to confirm the minimum fixed version for 12.2.x
  2. Review the Oracle E-Business Suite 12.2.15 or later release notes for Workflow Notification Mailer security fixes
  3. Plan upgrade considering Oracle's upgrade documentation for EBS 12.2.x
  4. Apply the upgrade in a non-production environment first to validate
  5. Test Workflow Notification Mailer functionality after upgrade
  6. Deploy to production
Caveat Review Oracle EBS 12.2.15 release notes for any mandatory upgrade requirements or deprecated features; Oracle EBS upgrades may require additional patching for integrated products

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

Fix this in Workflow Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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