CVE-2026-60821: Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: Business In...
Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: Business Interlink). Supported versions that are affected are 8.61-8.63. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks of this vulnerability can result in takeover of PeopleSoft Enterprise PeopleTools. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Security readout for executives and security teams
Plain-English summary
An attacker who can reach a vulnerable PeopleSoft PeopleTools system over HTTP may take it over without credentials or user interaction. A successful attack could expose sensitive data, alter business processes or records, and disrupt service. The reported severity is critical, with a 9.8 CVSS score. The supplied sources do not establish observed exploitation.
Executive priority
Treat this as an urgent exposure-verification and remediation issue. Prioritize internet-facing and business-critical PeopleTools systems, restrict unnecessary HTTP reachability, and follow Oracle guidance. Although the bundle provides no active-exploitation evidence, unauthenticated remote takeover potential and a 9.8 score justify immediate ownership and tracking.
Technical view
CVE-2026-60821 concerns Business Interlink in supported PeopleTools 8.61-8.63. Classified under access-control and missing-authentication weaknesses, it is network-exploitable over HTTP, low complexity, requires no privileges or user interaction, and can cause complete confidentiality, integrity, and availability loss. The structured affected field lists only 8.61, so precise release scope requires Oracle confirmation.
Likely exposure
Exposure is highest where affected PeopleTools HTTP services are reachable from the internet or untrusted networks. Internal-only systems remain at risk from attackers with a network path. The description identifies releases 8.61-8.63, although the structured affected list names only 8.61. The bundle provides no deployment-prevalence information.
Exploitation context
The source bundle does not identify KEV inclusion, active exploitation, a public proof of concept, or attack indicators. It does state that exploitation is easy, unauthenticated, and remotely reachable through HTTP. Absence of confirmed exploitation should not be interpreted as low risk, especially for externally reachable systems.
Researcher notes
The bundle maps the issue to CWE-284 and CWE-306 but provides no root-cause detail, indicators, proof of concept, or specific remediation text. Researchers should avoid assuming Business Interlink non-use removes exposure. The conflicting version representations and exact remediation status should be verified directly against Oracle's advisory.
Mitigation direction
Consult Oracle's August 2026 advisory and apply its remediation for the exact PeopleTools release as soon as confirmed.
Restrict PeopleTools HTTP access to trusted networks and authorized administrative paths while remediation is pending.
Isolate affected instances that cannot be promptly remediated, particularly those reachable from the internet.
Preserve and review relevant access and administrative logs for suspicious activity or unauthorized changes.
Validation and detection
Inventory all PeopleTools deployments and record versions, support status, HTTP exposure, and Business Interlink presence.
Compare each instance against Oracle's advisory and resolve the 8.61 versus 8.61-8.63 scope discrepancy.
Confirm vendor-recommended remediation is applied successfully using approved configuration and version records.
Review HTTP access controls and verify affected services are not unintentionally reachable from untrusted networks.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authentication for Critical Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.