dbcve.org
Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2026-21951

MEDIUM · 6.1 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 →
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: Integration Broker). Supported versions that are affected are 8.60, 8.61 and 8.62. 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 (scope change). 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

Injection vulnerability in Oracle PeopleSoft Enterprise PeopleTools Integration Broker component (versions 8.60, 8.61, 8.62) allows unauthenticated remote attackers via HTTP to achieve unauthorized read and limited write/delete access to some accessible data. Exploitation requires human interaction (victim must perform some action) and may impact additional products due to scope change.

MitigationApply Oracle Critical Patch Updates for PeopleSoft when available; restrict network access to Integration Broker endpoints; review and harden Integration Broker security configurations; implement web application firewall rules for injection 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 Enterprise PeopletoolsApplication
Affected:= 8.60= 8.61= 8.62

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. Check PeopleSoft PeopleTools version
    Log into PeopleSoft and navigate to PeopleTools > Utilities > About, or query the PSVERSION table for the current tools version (select * from PSVERSION where OBJECTTYPENAME='TOOLS').
    Affected if The installed PeopleTools version is exactly 8.60, 8.61, or 8.62.
  2. Verify Integration Broker is enabled
    Navigate to PeopleTools > Integration Broker > Integration Setup > Service Configuration, or check the IB domain status via psadmin utility (psadmin -list), to determine if Integration Broker is configured and running.
    Affected if Integration Broker service is enabled and the IB domain is active.
  3. Confirm HTTP endpoints are exposed
    Check the Integration Broker gateway URL configuration (PeopleTools > Integration Broker > Gateway Setup > Gateway) and verify if the HTTP (non-SOAP) handler is accessible externally. Test connectivity to the IBT_GATEWAY web service endpoint.
    Affected if Integration Broker HTTP endpoints are accessible over network (not restricted to localhost/internal network).
  4. Check for unauthenticated service operations
    Review Integration Broker service operations in PeopleTools > Integration Broker > Service Operation Monitor > Service Operations, and identify any service operations that allow anonymous or unauthenticated access.
    Affected if Any Integration Broker service operations are configured to allow anonymous or unauthenticated access.

The environment is affected if running PeopleTools version 8.60, 8.61, or 8.62 with Integration Broker enabled and its HTTP endpoints accessible to unauthenticated 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 Oracle Critical Patch Updates for PeopleSoft when available; restrict network access to Integration Broker endpoints; review and harden Integration Broker security configurations; implement web application firewall rules for injection patterns.

Fix this in Peoplesoft Enterprise Peopletools Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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