dbcve.org
Peoplesoft Supply Chain Management PurchasingApplication · Oracle

CVE-2026-21971

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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: Purchasing). 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 update, insert or delete access to some of PeopleSoft Enterprise SCM Purchasing accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise SCM Purchasing accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 is an injection-type vulnerability in the Purchasing component of PeopleSoft Enterprise SCM 9.2. It allows low-privileged attackers with network access via HTTP to perform unauthorized data manipulation (update, insert, delete) and read access to a subset of accessible data. The CVSS vector indicates a network-exploitable, low-complexity attack requiring only low privileges with no user interaction.

MitigationApply the Oracle Critical Patch Update for PeopleSoft Enterprise SCM 9.2 when available. If no patch exists, implement compensating controls such as restricting network access to the Purchasing module, reviewing user permissions, and monitoring for suspicious SQL patterns.

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 Supply Chain Management 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Verify PeopleSoft SCM version
    Access PeopleSoft About page (typically via PeopleTools > About This Page) or check the PSVERSION table in the database to confirm the application version number
    Affected if Version is exactly 9.2 and the Purchasing module is deployed
  2. Confirm Purchasing module is enabled
    Check PeopleSoft Component Registry (PeopleTools > Security > Component Permissions) or verify the PURCHASING application package is loaded in the current environment
    Affected if Purchasing component is active in the deployed system
  3. Verify HTTP access to Purchasing
    Check web profile configuration (PeopleTools > Web Profile > Security) and review which URLs/routes are exposed for the Purchasing component (typically /psc/.../Purchasing/*)
    Affected if HTTP/HTTP(s) network access to Purchasing component is enabled and publicly or broadly accessible
  4. Review low-privileged user access
    Query PeopleSoft security tables (PSROLEUSER, PSCLASSDEFN) or use PeopleTools > Security > User Profiles to enumerate which roles with low-level permissions include Purchasing component access
    Affected if Low-privileged or generic user accounts have Purchasing component access via assigned roles
  5. Inspect for SQL injection indicators
    Review PeopleSoft application server logs (APPSRV.LOG) and database audit logs for unusual SQL patterns, unexpected WHERE clauses, or UNION-based queries targeting PURCHASING-related tables
    Affected if Logs show anomalous SQL queries containing injection patterns against Purchasing tables

Your environment is affected if you run PeopleSoft Enterprise SCM exactly version 9.2 with the Purchasing module enabled and accessible via HTTP to low-privileged users.

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 for PeopleSoft Enterprise SCM 9.2 when available. If no patch exists, implement compensating controls such as restricting network access to the Purchasing module, reviewing user permissions, and monitoring for suspicious SQL patterns.

Fix this in Peoplesoft Supply Chain Management Purchasing Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21971 — 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-2026-21971 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