dbcve.org
Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2020-14813

MEDIUM · 6.1 CVSS v3.1 Published 2020-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: PIA Grids). Supported versions that are affected are 8.56, 8.57 and 8.58. 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.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/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 · moderate confidence

This vulnerability exists in the PIA (PeopleSoft Internet Architecture) Grids component of PeopleSoft Enterprise PeopleTools. It allows unauthenticated attackers with network access via HTTP to achieve unauthorized read and limited write/delete access to PeopleSoft data. The requirement for human interaction from a person other than the attacker suggests this may be a cross-site request forgery (CSRF) type flaw in the grid rendering or data submission process.

MitigationApply the Oracle Critical Patch Update (CPU) that addresses CVE-2020-14813 for the affected PeopleTools versions (8.56, 8.57, 8.58). Consider implementing CSRF tokens in PIA and restricting HTTP access to trusted networks until the patch can be applied.

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
Peoplesoft Enterprise PeopletoolsApplication
Affected:= 8.56= 8.57= 8.58

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify PeopleSoft PeopleTools version
    Check the PeopleTools version via the PS_HOME directory, or access PeopleSoft and look at the bottom-left corner of the PeopleSoft Internet Architecture (PIA) login page, or query the PSVERSION table in the database for the current tools release version.
    Affected if The installed PeopleTools version is 8.56, 8.57, or 8.58.
  2. Confirm PIA Grids component is accessible
    Verify that the PeopleSoft Internet Architecture (PIA) web component is deployed and accessible. Access a PeopleSoft page that uses the Grids component (such as a list or data grid view) via the web browser without authentication.
    Affected if PIA Grids are accessible without authentication over HTTP.
  3. Check HTTP listener configuration
    Review the web server configuration (typically Oracle WebLogic or IBM HTTP Server) to determine if HTTP (port 80/443) listeners accept unauthenticated connections to the PSIGW or PSEMHUB servlets used by PIA grids.
    Affected if HTTP listeners accept unauthenticated requests to PeopleSoft applications.
  4. Inspect CSRF token enforcement
    Review the PeopleSoft application configuration files (such as web.xml and psconfig.sh) or attempt a grid data submission without a valid CSRF token to see if the application rejects the request.
    Affected if CSRF tokens are not enforced or validated in grid data operations.

A system is affected if it runs PeopleSoft Enterprise PeopleTools versions 8.56, 8.57, or 8.58 with the PIA Grids component accessible via unauthenticated HTTP without CSRF protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2020-14813 for the affected PeopleTools versions (8.56, 8.57, 8.58). Consider implementing CSRF tokens in PIA and restricting HTTP access to trusted networks until the patch can be applied.

Fix this in Peoplesoft Enterprise Peopletools Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14813 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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