CVE-2020-14865
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 PeopleSoft Enterprise SCM eSupplier Connection product of Oracle PeopleSoft (component: eSupplier Connection). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise SCM eSupplier Connection. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise SCM eSupplier Connection accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise SCM eSupplier Connection accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 · moderate confidenceCVE-2020-14865 is a vulnerability in PeopleSoft Enterprise SCM eSupplier Connection version 9.2. The flaw allows a low-privileged attacker with network access via HTTP to bypass authorization controls, enabling unauthorized creation, deletion, or modification of critical data, as well as complete read access to all accessible data in the eSupplier Connection module.
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= 9.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Confirm PeopleSoft Enterprise SCM installationCheck if Oracle PeopleSoft Enterprise SCM components are installed on the system by reviewing installed applications or consulting system inventoryAffected if PeopleSoft Enterprise SCM is not installed - not affected
-
Verify eSupplier Connection module is enabledCheck if the eSupplier Connection module is configured and active within the PeopleSoft environment by reviewing the application module configuration or consulting the PeopleSoft administratorAffected if eSupplier Connection module is not enabled - not affected
-
Confirm eSupplier Connection versionCheck the installed version of the eSupplier Connection module. This can typically be found in PeopleSoft About pages, version information screens, or by querying the PeopleSoft application for module version detailsAffected if Version is 9.2 - affected; version differs from 9.2 - not affected based on provided version range
-
Assess network exposure of HTTP endpointsDetermine if the eSupplier Connection HTTP endpoints are accessible from the network. Review firewall rules, web server configuration, and network access controls for PeopleSoft web servicesAffected if HTTP endpoints are exposed to network - vulnerable attack surface exists; endpoints are internal-only - reduced risk but version still matters
-
Review user permission configurationCheck the privilege level of user accounts that can access eSupplier Connection. Identify if low-privileged users have access to create, delete, or modify data operationsAffected if Low-privileged users can access eSupplier Connection - potential for exploitation
You are affected if eSupplier Connection version is exactly 9.2 AND the module is enabled AND network access to its HTTP endpoints exists.
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 latest Oracle Critical Patch Update for PeopleSoft or implement compensating controls such as restricting network access to eSupplier Connection endpoints and enforcing least-privilege user permissions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14865 — 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-14865 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