dbcve.org
E Business SuiteApplication · Oracle

CVE-2026-47028

HIGH · 8.1 CVSS v3.1 Published 2026-07-21
Fix available
A fix is available. Upgrade to after 12.2.15 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 4 weeks old

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 Document Management and Collaboration product of Oracle E-Business Suite (component: Attachments). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Document Management and Collaboration. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Document Management and Collaboration accessible data as well as unauthorized access to critical data or complete access to all Oracle Document Management and Collaboration 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 Document Management and Collaboration (Attachments component) allows low-privileged attackers with network access via HTTP to perform unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to critical or all accessible data. The attack has high confidentiality and integrity impact but no availability impact.

MitigationApply the relevant Oracle patch for this vulnerability when released. In the interim, restrict network access to the Oracle E-Business Suite Document Management interfaces and monitor for suspicious attachment-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
E Business SuiteApplication
Affected:>= 12.2.3, <= 12.2.15

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
    Check for Oracle E-Business Suite processes or services running on application servers. Common process names include 'FNDSM', 'FNDLOAD', or look for Oracle WebLogic/Apache configurations serving EBS paths.
    Affected if Oracle E-Business Suite is installed and running in the environment
  2. Determine the E-Business Suite version
    Query the database or application server for the EBS version. This is typically available through the Oracle Application Manager interface, or by querying the FND_PRODUCT_GROUPS or FND_VERSION tables in the Oracle database.
    Affected if The installed version falls within the affected range (verify against Oracle's official advisory for your specific version)
  3. Verify Document Management and Collaboration module is enabled
    Check the Oracle E-Business Suite module configuration. Access System Administrator responsibility, navigate to Application > Register and verify if 'Document Management Collaboration' or 'Attachments' component is installed and enabled.
    Affected if The Document Management and Collaboration (Attachments) module is enabled in the EBS instance
  4. Confirm HTTP network accessibility
    Test if the EBS web interfaces (typically on ports 8000-8004 or 443) are exposed over HTTP/HTTPS. Use curl or a browser to verify the Attachments/Document Management endpoints are reachable.
    Affected if The E-Business Suite web interfaces are accessible over the network via HTTP
  5. Review user access privileges to Attachments functionality
    Check which user roles have access to the Attachments or Document Management functionality. Navigate to Security > Define and review role assignments for low-privileged users.
    Affected if Low-privileged users or roles have network access to the Attachments component

The environment is likely affected if Oracle E-Business Suite with Document Management and Collaboration (Attachments) is enabled and accessible over the network 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.

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

Apply the relevant Oracle patch for this vulnerability when released. In the interim, restrict network access to the Oracle E-Business Suite Document Management interfaces and monitor for suspicious attachment-related activity.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.16 or later (if available)

  1. 1. Subscribe to Oracle Critical Patch Updates to receive security patches: https://www.oracle.com/security-alerts/
  2. 2. Apply the latest Oracle Critical Patch Update (CPU) that includes the fix for CVE-2026-47028
  3. 3. Alternatively, check Oracle Support for patch numbers specific to Oracle E-Business Suite 12.2.x security vulnerabilities
  4. 4. After applying the patch, verify the fix by testing the Attachments functionality in Oracle Document Management and Collaboration
  5. 5. Review Oracle E-Business Suite security hardening guides for additional mitigations
Caveat Oracle patch applications may require downtime and thorough testing in a non-production environment first

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

Fix this in E Business Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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