CVE-2020-2751
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 PeopleTools product of Oracle PeopleSoft (component: Portal). Supported versions that are affected are 8.56 and 8.57. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise PeopleTools, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise PeopleTools accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.0 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 confidenceCVE-2020-2751 is an unauthenticated vulnerability in the PeopleSoft Enterprise PeopleTools Portal component (versions 8.56 and 8.57). Attackers can exploit this via HTTP network requests, but require human interaction to succeed. The flaw allows unauthorized read and write access to a subset of accessible data within the PeopleSoft Portal.
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= 8.56= 8.57CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Identify the installed PeopleTools versionLog into PeopleSoft Application Designer or access the PeopleSoft About page (usually via Help > About PeopleSoft Application Designer or /about.html endpoint). Alternatively, query the PSVERSION table or check the PS_HOME directory for version files.Affected if The installed PeopleTools version is 8.56 or 8.57
-
Confirm the Portal component is enabledCheck if the PeopleSoft Portal (Employee Self-Service, Candidate Gateway, or generic Portal) is configured and accessible. Look for portal-related services in the web profile configuration or check if /psc/ or /psp/ URL paths respond.Affected if The Portal component is enabled and responding to HTTP requests
-
Verify HTTP network exposure of the PortalReview network configuration to determine if the Portal URLs are reachable from external or untrusted networks. Check load balancer, web server, or firewall rules that expose the PeopleSoft web URLs (typically ports 80/443 or custom web server ports).Affected if The Portal is accessible from untrusted or external networks without proper access restrictions
-
Check for signs of unauthorized accessReview PeopleSoft security logs, access logs, and audit tables (such as PSAUDIT or web server logs) for unusual or unauthenticated requests to portal-related servlets, particularly from unknown IP addresses.Affected if Unusual unauthenticated access patterns to portal servlets are found in logs
A system is affected if it runs PeopleTools version 8.56 or 8.57 with the Portal component enabled and exposed to network access, making it vulnerable to unauthenticated HTTP-based attacks.
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 relevant Oracle PeopleSoft Enterprise PeopleTools patch for versions 8.56/8.57 to address the Portal vulnerability, and restrict HTTP access to the Portal from untrusted networks until patching is feasible.
- 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-2751 — 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-2751 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