dbcve.org
Peoplesoft Enterprise Fin ContractsApplication · Oracle

CVE-2026-34300

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-21
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 FIN Contracts product of Oracle PeopleSoft (component: Contracts). 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 FIN Contracts. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise FIN Contracts accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/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 · moderate confidence

A vulnerability in PeopleSoft Enterprise FIN Contracts version 9.2 allows a low-privileged attacker with network access via HTTP to gain unauthorized access to critical data. The vulnerability has high confidentiality impact with no integrity or availability impact, suggesting it may be a broken access control or similar authorization flaw in the Contracts component.

MitigationApply the Oracle PeopleSoft security patch when available. Until then, restrict network access to the PeopleSoft HTTP endpoints to trusted IPs only and audit user permissions in the FIN Contracts module following least-privilege principles.

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 Fin ContractsApplication
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. Identify installed PeopleSoft FIN Contracts version
    Access PeopleSoft Application Designer or the About page in PeopleSoft Enterprise to view the FIN Contracts component version. Alternatively, query the PSVERSION table or check the installation manifest for the exact version number of the FIN Contracts module.
    Affected if The installed FIN Contracts version is exactly 9.2
  2. Confirm FIN Contracts web component is enabled
    Log into PeopleSoft Enterprise and navigate to the FIN Contracts module through the menu structure. Verify the Contracts component is accessible and loaded in the web application.
    Affected if The FIN Contracts module is accessible and the component loads successfully
  3. Check network accessibility of PeopleSoft HTTP endpoints
    Determine if the PeopleSoft Application Server HTTP port is exposed to untrusted networks. Use a browser or curl command from an untrusted network location to confirm whether the /psc/ or /psp/ HTTP endpoints are reachable externally.
    Affected if The PeopleSoft HTTP endpoints are reachable from untrusted or external network locations
  4. Audit user permissions in FIN Contracts
    Review role and permission list assignments for users with access to the FIN Contracts module using PeopleSoft Security Administrator. Check which low-privileged users have been granted access to Contracts-related components and data.
    Affected if Low-privileged users with limited or basic roles have been granted access to view critical Contracts data

A user is affected if they have FIN Contracts version 9.2 deployed with the HTTP interface accessible to untrusted networks and users with low privileges can access sensitive contract data.

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 PeopleSoft security patch when available. Until then, restrict network access to the PeopleSoft HTTP endpoints to trusted IPs only and audit user permissions in the FIN Contracts module following least-privilege principles.

Fix this in Peoplesoft Enterprise Fin Contracts Scoped from the published advisory
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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