CVE-2026-46884
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 Siebel Apps - Marketing product of Oracle Siebel CRM (component: Marketing). Supported versions that are affected are 17.0-26.5. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Siebel Apps - Marketing. Successful attacks of this vulnerability can result in takeover of Siebel Apps - Marketing. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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 confidenceUnauthenticated remote code execution vulnerability in Oracle Siebel CRM Marketing component (versions 17.0-26.5). The flaw is network-exploitable via HTTP with no authentication or user interaction required, allowing complete system takeover (full confidentiality, integrity, and availability compromise).
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>= 17.0, <= 26.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Oracle Siebel Marketing component is installedLocate the Siebel installation directory and check for the Marketing module. Common paths include Siebel home directory under /siebel/ or C:\siebel\. Look for components named 'Siebel Marketing' or 'Mktg' in the installation.Affected if The Marketing component is present on the system
-
Determine the installed version of Siebel Apps MarketingCheck the Siebel version information. This is typically available via the Siebel Enterprise Server administration console, the installation logs, or by querying the Siebel repository database. The version format appears as numeric (e.g., 17.0, 18.0, 22.0, 26.5).Affected if The installed version falls within the range 17.0 through 26.5 inclusive
-
Verify if HTTP network exposure is enabled for Marketing interfacesReview Siebel Web Server configuration files (such as eapps.cfg or web.xml) to determine if the Marketing application is accessible via HTTP/HTTPS. Check the Siebel Gateway and Enterprise Server configuration for exposed application interfaces.Affected if The Marketing component is configured to accept HTTP connections and is network-reachable
-
Confirm if unauthenticated access to Marketing URLs is possibleTest accessing Siebel Marketing URLs (typically under /siebel/marketing/ or similar paths) without providing credentials. Use a browser or curl command to attempt unauthenticated access to the Marketing application endpoint.Affected if The Marketing interface accepts requests without requiring authentication
-
Review network accessibility of Siebel Marketing portsPerform a network port scan to identify open ports serving Siebel applications. Siebel Marketing commonly runs on ports 80, 443, 8080, or 8443. Check firewall rules and network segmentation for these ports.Affected if Siebel Marketing ports are exposed to untrusted networks without proper network-level access controls
You are affected if Oracle Siebel Apps Marketing versions 17.0 through 26.5 are installed, the Marketing component is network-accessible via HTTP, and the interface permits unauthenticated 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 Oracle's available patch for this vulnerability immediately. Until patched, restrict network access to Siebel Marketing interfaces and implement Web Application Firewall (WAF) rules to detect exploitation attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46884 — 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-46884 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