CVE-2026-60941
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 · uneditedVulnerability in the Oracle Service Fulfillment Manager product of Oracle E-Business Suite (component: Fulfillment Engine). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Service Fulfillment Manager. While the vulnerability is in Oracle Service Fulfillment Manager, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Service Fulfillment Manager accessible data as well as unauthorized access to critical data or complete access to all Oracle Service Fulfillment Manager accessible data. CVSS 3.1 Base Score 8.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 · high confidenceVulnerability in Oracle Service Fulfillment Manager's Fulfillment Engine allows high-privileged attackers with network HTTP access to create, delete, or modify critical data, and gain unauthorized access to data. The attack may impact additional products beyond the immediate component due to scope change. Affects Oracle E-Business Suite versions 12.2.3 through 12.2.15.
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>= 12.2.3, <= 12.2.15CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Service Fulfillment Manager installationLocate Oracle Service Fulfillment Manager installation directories and verify the product is present in the environment. Check for Oracle FMS home directories or application servers hosting this component.Affected if Oracle Service Fulfillment Manager is installed and the version falls within 12.2.3-12.2.15
-
Determine installed Fulfillment Manager versionQuery the installed version using Oracle inventory tools, check version files within the FMS installation directory, or use the Oracle opatch lsinventory command to list installed Oracle components and versions.Affected if The installed version is 12.2.3, 12.2.4, 12.2.5, 12.2.6, 12.2.7, 12.2.8, 12.2.9, 12.2.10, 12.2.11, 12.2.12, 12.2.13, 12.2.14, or 12.2.15
-
Verify Fulfillment Engine HTTP accessibilityCheck if the Fulfillment Engine component is exposed via HTTP/HTTPS endpoints. Review web server configurations, application URLs, and load balancer rules that route traffic to the Fulfillment Engine component.Affected if The Fulfillment Engine component is network-accessible via HTTP without proper restrictions
-
Review Fulfillment Engine access controlsExamine the Fulfillment Engine configuration and access control lists to determine what level of privilege is required for HTTP access. Verify whether low-privileged or anonymous users can reach the component.Affected if HTTP access to Fulfillment Engine is granted to users without high-privilege requirements or access is inadequately restricted
-
Assess network exposure of Fulfillment EngineReview network segmentation, firewall rules, and API gateway policies to determine if the Fulfillment Engine component is accessible from untrusted networks rather than only from trusted administrative segments.Affected if The Fulfillment Engine is accessible from network segments that do not require high-privilege authentication
You are affected if Oracle Service Fulfillment Manager versions 12.2.3-12.2.15 are installed AND the Fulfillment Engine component is accessible via HTTP to attackers who may not have high privileged access.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the Oracle Critical Patch Update for Oracle E-Business Suite addressing the Service Fulfillment Manager vulnerability. Since this requires high privileges, restrict administrative access and monitor for anomalous fulfillment engine operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-60941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60941 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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