Peoplesoft Enterprise Scm PurchasingApplication · Oracle

CVE-2020-2906

MEDIUM · 6.5 CVSS v3.1 Published 2020-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 SCM Purchasing product of Oracle PeopleSoft (component: Supplier Change). 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 Purchasing. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise SCM Purchasing accessible data. CVSS 3.0 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 confidence

This is an Oracle PeopleSoft Enterprise SCM Purchasing vulnerability affecting the Supplier Change component in version 9.2. A low-privileged attacker with network access via HTTP can exploit this to gain unauthorized access to critical data, achieving high confidentiality impact.

MitigationApply the relevant Oracle Critical Patch Update for CVE-2020-2906 to the PeopleSoft Enterprise SCM Purchasing 9.2 environment. If no patch is available, consider restricting network access to the Purchasing module and reviewing user privileges.

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 Scm PurchasingApplication
Affected:= 9.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm PeopleSoft SCM Purchasing version
    Access PeopleSoft Application Designer or navigate to PeopleTools > About PeopleSoft to verify the installed version of Oracle PeopleSoft Enterprise SCM Purchasing is exactly 9.2
    Affected if The installed version is PeopleSoft Enterprise SCM Purchasing 9.2
  2. Verify Supplier Change component is configured
    In PeopleSoft Application Designer, search for the Supplier Change component (typically under Enterprise Components > Supplier Change) or check if the component exists in the system
    Affected if The Supplier Change component is present and deployed in the environment
  3. Check HTTP accessibility of Purchasing module
    Attempt to access the Purchasing module via web browser using the PeopleSoft HTTP/HTTPS URL (e.g., /psc/ps/EMPLOYEE/SCM/c/FRAME_R.FRAME_R.GBL)
    Affected if The Purchasing module is accessible over HTTP/HTTPS from the network
  4. Review low-privilege user access to Supplier Change
    In PeopleSoft Security, check permission lists and roles assigned to low-privileged users to determine if they have access to the Supplier Change component (look for Component permissions in the component security settings)
    Affected if Low-privileged users (with basic or limited roles) have access to the Supplier Change component

A user is affected if they have Oracle PeopleSoft Enterprise SCM Purchasing version 9.2 with the Supplier Change component enabled and accessible to low-privileged users via HTTP.

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 relevant Oracle Critical Patch Update for CVE-2020-2906 to the PeopleSoft Enterprise SCM Purchasing 9.2 environment. If no patch is available, consider restricting network access to the Purchasing module and reviewing user privileges.

Fix this in Peoplesoft Enterprise Scm Purchasing Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2906 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2906 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