dbcve.org
Peoplesoft Enterprise Fin Project CostingApplication · Oracle

CVE-2026-34306

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 Project Costing product of Oracle PeopleSoft (component: Projects). 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 Project Costing. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise FIN Project Costing 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

Information disclosure vulnerability in PeopleSoft Enterprise FIN Project Costing 9.2 (Projects component). A low-privileged attacker with network access via HTTP can exploit this to gain unauthorized access to sensitive project costing data.

MitigationApply the relevant Oracle Critical Patch Update for PeopleSoft Enterprise FIN Project Costing 9.2. In the interim, restrict network access to PeopleSoft HTTP endpoints and review low-privileged user access controls.

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 Project CostingApplication
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 FIN Project Costing version
    Access PeopleSoft Application Designer or check the About PeopleSoft page in the browser. Navigate to PeopleTools > About in the PIA (PeopleSoft Internet Architecture) to view installed product versions.
    Affected if The installed version is exactly 9.2 or falls within the 9.2 product line for Enterprise FIN Project Costing
  2. Verify Projects component is enabled
    Log into PeopleSoft and navigate to the Projects component. Check if the component is available in the menu structure under Enterprise FIN Project Costing.
    Affected if The Projects component (component name likely PROJECT or similar in the Projects module) is present and accessible in the application
  3. Check HTTP accessibility of PeopleSoft endpoints
    Verify that the PeopleSoft web server (PIA) HTTP/HTTPS ports are accessible. Attempt to access the Projects component URL path via HTTP from a network location.
    Affected if PeopleSoft HTTP endpoints are exposed and accessible over the network (not restricted to localhost or VPN)
  4. Review low-privileged user access to project data
    In PeopleSoft Security, navigate to PeopleTools > Security > User Profiles or Role permissions. Check if standard or low-privileged users have access to view project costing data through the Projects component.
    Affected if Low-privileged users (non-admin, non-superuser roles) have query or read access to the Projects component and associated project costing data

Your environment is affected if you run PeopleSoft Enterprise FIN Project Costing version 9.2, have the Projects component enabled, expose HTTP access to the application, and low-privileged users can access project costing 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 relevant Oracle Critical Patch Update for PeopleSoft Enterprise FIN Project Costing 9.2. In the interim, restrict network access to PeopleSoft HTTP endpoints and review low-privileged user access controls.

Fix this in Peoplesoft Enterprise Fin Project Costing Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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