dbcve.org
Financials Common ModulesPlugin / extension · Oracle

CVE-2026-46821

HIGH · 7.7 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to after 12.2.15 or later.
See remediation →
83/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 Financials Common Modules product of Oracle E-Business Suite (component: Common Components). 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 Financials Common Modules. While the vulnerability is in Oracle Financials Common Modules, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Financials Common Modules accessible data. CVSS 3.1 Base Score 7.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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

Vulnerability in Oracle Financials Common Modules (part of Oracle E-Business Suite) allows low-privileged attackers with network access via HTTP to gain unauthorized access to critical data. The CVSS 3.1 score of 7.7 reflects high confidentiality impact with scope change, meaning attacks can affect additional products beyond the directly affected component.

MitigationApply Oracle's security patches for the affected E-Business Suite versions (12.2.3-12.2.15) and implement network access controls to limit exposure to the Oracle Financials interfaces until patches are deployed.

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
Financials Common ModulesPlugin / extension
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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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 Financials Common Modules version
    Query the Oracle database for the installed version. In Oracle E-Business Suite, this can be checked via the FND_PRODUCT_INSTALLATIONS table or by querying the version from the Oracle Applications responsibility menu. Alternatively, check the Oracle E-Business Suite readme or about page for the Financials module version.
    Affected if Version is 12.2.3 through 12.2.15 (inclusive)
  2. Verify HTTP interface accessibility
    Determine if Oracle E-Business Suite HTTP services (OAF/OA Framework pages) for Financials are accessible from the network. Check the web listener configuration and test access to Financials module URLs.
    Affected if HTTP interfaces are exposed to untrusted networks without restricted access controls

Environment is affected if Oracle Financials Common Modules version is 12.2.3-12.2.15 and the HTTP interface 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.

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

Apply Oracle's security patches for the affected E-Business Suite versions (12.2.3-12.2.15) and implement network access controls to limit exposure to the Oracle Financials interfaces until patches are deployed.

Recommended fix Moderate confidence

Apply Oracle's latest Critical Patch Update for Oracle E-Business Suite; Oracle typically addresses such vulnerabilities in quarterly patch releases. Contact Oracle Support for the specific patched version (after 12.2.15) that addresses CVE-2026-46821.

  1. 1. Identify the current Oracle E-Business Suite Financials Common Modules version by navigating to the Oracle Applications DBA responsibility and checking the version.
  2. 2. Confirm the installed version falls within the affected range of 12.2.3 to 12.2.15.
  3. 3. Contact Oracle Support or access the Oracle Critical Patch Updates advisory to obtain the specific patch for this vulnerability (CVE-2026-46821).
  4. 4. Apply the appropriate Oracle E-Business Suite patch following Oracle's standard patching procedures, which typically involves: running the adop utility in prepare mode, applying the patch, running adop in finalize mode, and running adop in complete mode.
  5. 5. After patching, verify the Financials Common Modules version has been updated and confirm the vulnerability is resolved through Oracle's standard verification methods.
Caveat Standard Oracle E-Business Suite patching carries standard risks - always test patches in a non-production environment before applying to production. Review Oracle's patch pre-install requirements and ensure backups are available.

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

Fix this in Financials Common Modules 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-2026-46821 — 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-46821 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