dbcve.org
Subledger AccountingWeb browser · Oracle

CVE-2026-46959

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 12.2.15 or later.
See remediation →
81/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 Subledger Accounting product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Subledger Accounting. Successful attacks of this vulnerability can result in takeover of Oracle Subledger Accounting. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).

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 Subledger Accounting (Internal Operations component) of Oracle E-Business Suite versions 12.2.3-12.2.15. A low-privileged attacker with network access via HTTP can exploit this difficult-to-exploit flaw to potentially take over the Oracle Subledger Accounting module, with high impact on confidentiality, integrity, and availability.

MitigationApply the relevant Oracle Critical Patch Update for Oracle E-Business Suite to address this vulnerability in the Subledger Accounting component.

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
Subledger AccountingWeb browser
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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

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
    Query the Oracle database for the release version using SQL: SELECT release_name FROM apps.fnd_product_groups; or check the $APPL_TOP/../comn/shared/appsutil/XX directories for version files.
    Affected if The installed E-Business Suite version falls within 12.2.3 to 12.2.15 inclusive.
  2. Confirm Subledger Accounting module is installed
    Query the Oracle database: SELECT application_id, application_name FROM fnd_application WHERE application_name LIKE '%Subledger Accounting%' OR application_name LIKE '%SLA%'; or check Oracle Applications Manager (OAM) for installed modules.
    Affected if The Subledger Accounting (SLA) module is present in the environment.
  3. Verify HTTP access to Oracle E-Business Suite is enabled
    Check if the Oracle HTTP Server (OHS) or Apache listener is running and accepting connections on ports 8000-8009 typically used by E-Business Suite. Run: netstat -an | grep -E '800[0-9]|443|80' or check the $ORACLE_HOME/Apache/Apache/conf/httpd.conf configuration.
    Affected if HTTP/HTTPS access to E-Business Suite is enabled and the application is reachable over the network.
  4. Check for low-privileged user accounts with Subledger Accounting access
    Query responsibilities assigned to low-privileged users: SELECT fr.responsibility_name, fu.user_name, fu.end_date FROM fnd_responsibility_vl fr, fnd_user_resp_groups_direct fu WHERE fr.responsibility_id = fu.responsibility_id AND (fr.responsibility_name LIKE '%Subledger%' OR fr.responsibility_name LIKE '%SLA%');
    Affected if Low-privileged users have active responsibilities granting access to the Subledger Accounting module.
  5. Review audit logs for suspicious Subledger Accounting activity
    Examine Oracle Audit Vault or standard Oracle audit records: SELECT timestamp, username, action_name, obj_name FROM dba_audit_trail WHERE obj_name LIKE '%SLA%' OR action_name IN ('INSERT','UPDATE','DELETE') AND timestamp > SYSDATE-30;
    Affected if Unusual or unauthorized activity is found in Subledger Accounting audit records from low-privileged accounts.

Your environment is affected if Oracle E-Business Suite version 12.2.3 through 12.2.15 is installed, the Subledger Accounting module is present, and it is accessible via HTTP with low-privileged user accounts able to access it.

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 Critical Patch Update for Oracle E-Business Suite to address this vulnerability in the Subledger Accounting component.

Recommended fix Moderate confidence

Apply the latest Oracle E-Business Suite Critical Patch Update (CPU). Oracle E-Business Suite 12.2.15 is the latest in the 12.2.x family; confirm the CPU includes the fix for CVE-2026-46959.

  1. 1. Subscribe to Oracle Critical Patch Updates to receive security patches: https://www.oracle.com/security-alerts/
  2. 2. Apply the latest Oracle E-Business Suite Critical Patch Update (CPU) that addresses this vulnerability
  3. 3. After applying the patch, verify the fix by confirming the Oracle Subledger Accounting component has been updated
  4. 4. Test the Oracle Subledger Accounting Internal Operations functionality to ensure normal operations are not impacted
  5. 5. Validate that the patch was applied successfully by checking the Oracle applications version or using Oracle ADPatch utility logs
Caveat Oracle CPU patches are cumulative and typically include multiple fixes; regression testing of affected functionality (Subledger Accounting Internal Operations) is recommended after applying the patch.

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

Fix this in Subledger Accounting Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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