CVE-2020-2794
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 Email Center product of Oracle E-Business Suite (component: Email Address list and Message Display). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Email Center. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Email Center, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Email Center accessible data as well as unauthorized update, insert or delete access to some of Oracle Email Center accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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 confidenceCross-site scripting (XSS) vulnerability in Oracle Email Center's Email Address List and Message Display component. Unauthenticated attackers can inject malicious scripts via HTTP that execute when other users view the affected email content, allowing unauthorized access to sensitive data and limited data modification.
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.1.1, <= 12.1.3>= 12.2.3, <= 12.2.9CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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.
-
Confirm Oracle Email Center is installedLocate the Oracle Email Center installation directory or check Oracle Application Server/Oracle WebLogic inventory for Email Center components. On Oracle E-Business Suite, navigate to the Email Center module through the application menu.Affected if Oracle Email Center product is present in the environment
-
Identify installed Oracle Email Center versionAccess the Email Center administrative interface or check the Oracle application version banner. For Oracle E-Business Suite, query the FND_PRODUCT_GROUPS table or check the About Oracle Email Center page.Affected if Installed version falls within 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.9
-
Verify Email Address List and Message Display component is enabledCheck Oracle Email Center configuration settings to confirm the Email Address List and Message Display component is active. Access the component through the Email Center console.Affected if The Email Address List and Message Display component is enabled and accessible to users
-
Inspect HTTP endpoints handling email contentReview HTTP request logs or access logs for the Email Center application. Look for endpoints that process email addresses and message display functionality. Common paths include /email/addressList or /email/messageDisplay endpoints.Affected if HTTP endpoints for email address list and message display are exposed without proper input sanitization filters
-
Test for reflected XSS in email parametersSubmit HTTP requests with malicious script payloads in email-related parameters (such as sender address, recipient address, or subject) to the Email Center endpoints and observe if the payload is reflected unescaped in the response.Affected if Script payloads are rendered directly in the browser without HTML encoding when viewing email content
The environment is affected if Oracle Email Center versions 12.1.1-12.1.3 or 12.2.3-12.2.9 are installed with the Email Address List and Message Display component enabled and accessible via HTTP.
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 Critical Patch Update (CPU) for April 2020. As interim measure, deploy WAF rules to filter malicious script payloads in HTTP requests to Email Center endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2794 — 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-2020-2794 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