CVE-2026-34299
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 · uneditedVulnerability in the PeopleSoft Enterprise FIN Maintenance Management product of Oracle PeopleSoft (component: Work Order Management). 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 Maintenance Management. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise FIN Maintenance Management 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 confidenceVulnerability in PeopleSoft Enterprise FIN Maintenance Management (Work Order Management component) allows low privileged attackers with network access via HTTP to compromise the system. Successful attacks result in unauthorized access to critical data or complete access to all accessible data, with confidentiality impact rated as High.
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= 9.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify PeopleSoft FIN Maintenance Management versionLog into PeopleSoft Enterprise Navigator or check the PeopleSoft version via the About page (Help > About). Alternatively, query the PSVERSION table for the application release version.Affected if The installed version is exactly 9.2 (version equals 9.2)
-
Confirm Work Order Management component is provisionedAccess the Work Order Management module by navigating to Enterprise Components > Work Order Management or verify via PeopleSoft Administrator that the FIN Maintenance Management component is installed and active.Affected if Work Order Management component is installed and accessible in the FIN module
-
Verify HTTP network exposureCheck if the PeopleSoft web server HTTP/HTTPS ports (typically ports 80, 443, or custom ports) are accessible from untrusted networks. Use network scanning or review firewall rules to confirm external accessibility.Affected if The PeopleSoft web interface is reachable from untrusted/network-accessible hosts
-
Review Work Order Management user permissionsAccess PeopleSoft Security Administrator (PeopleTools > Security > User Profiles) or Role Permissions (PeopleTools > Security > Roles & Permissions) and list users or roles granted access to the Work Order Management component (e.g., Work Order Administrator, Work Order User).Affected if Low-privileged users or roles have access to the Work Order Management component via HTTP
You are affected if you are running PeopleSoft Enterprise FIN Maintenance Management version 9.2 with the Work Order Management component enabled and accessible over HTTP to low-privileged users on untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Updates when available; in the interim, restrict network access to PeopleSoft systems to trusted sources only and review user permissions for the Work Order Management component.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-34299 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34299 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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