dbcve.org
WorkflowApplication · Oracle

CVE-2025-21541

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to after 12.2.14 or later.
See remediation →
60/100
Remediation priority · Elevated
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 Workflow product of Oracle E-Business Suite (component: Admin Screens and Grants UI). 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 Workflow. 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 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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

This is an access control vulnerability in Oracle E-Business Suite Oracle Workflow's Admin Screens and Grants UI component. A low-privileged attacker with network access via HTTP can exploit this to gain unauthorized read, insert, update, or delete access to a subset of Oracle Workflow data. The CVSS vector indicates this is exploitable over the network with low complexity and requires no user interaction, affecting versions 12.2.3 through 12.2.14.

MitigationApply Oracle Critical Patch Update (CPU) for January 2025 or later. If immediate patching is not feasible, review and restrict user role permissions within Oracle Workflow's Admin Screens and Grants UI to limit exposure.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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
    Locate the Oracle E-Business Suite installation directory or check for Oracle Application Server processes. Common locations include $ORACLE_HOME/apps or standard Oracle installation paths.
    Affected if Oracle E-Business Suite is not installed, the system is not affected by this CVE.
  2. Verify Oracle Workflow version
    Query the Oracle Workflow version using SQL: SELECT version FROM wf_version; or check the Oracle Applications Manager interface for the Workflow component version.
    Affected if The installed version is between 12.2.3 and 12.2.14 inclusive, the system falls within the affected version range.
  3. Confirm Oracle Workflow Admin Screens and Grants UI is accessible
    Check if the /OA_HTML/wf/ or /OA_HTML/wfgrants* endpoints are accessible via HTTP/HTTPS on the Oracle Applications web tier. Verify the Workflow administrative web interfaces are enabled.
    Affected if The Admin Screens and Grants UI component is exposed and accessible over the network, the vulnerability can be exploited.
  4. Check network exposure of Oracle Workflow
    Review firewall rules, load balancer configurations, and web server access controls to determine if the Oracle Workflow web interfaces are reachable from untrusted networks.
    Affected if The Workflow Admin interface is reachable from network segments accessible to low-privileged attackers, exploitation is possible.
  5. Review user role permissions in Oracle Workflow
    Use Oracle User Management to list roles assigned to low-privileged users who have access to the Workflow Admin Screens. Query: SELECT * FROM wf_user_roles WHERE role_name LIKE '%WFC%';
    Affected if Low-privileged users have access to the Admin Screens and Grants UI, they can potentially exploit this vulnerability.

The system is affected if Oracle E-Business Suite with Oracle Workflow versions 12.2.3 through 12.2.14 is installed and the Admin Screens and Grants UI component is network-accessible to low-privileged users.

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 Critical Patch Update (CPU) for January 2025 or later. If immediate patching is not feasible, review and restrict user role permissions within Oracle Workflow's Admin Screens and Grants UI to limit exposure.

Fix this in Workflow 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-21541 — 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-21541 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