dbcve.org
Peoplesoft Enterprise Fin Common ObjectsApplication · Oracle

CVE-2026-61074

HIGH · 8.1 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 4 weeks old

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 Common Objects Brazil product of Oracle PeopleSoft (component: eProcurement). The supported version that is affected is 9.1. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise FIN Common Objects Brazil. Successful attacks of this vulnerability can result in takeover of PeopleSoft Enterprise FIN Common Objects Brazil. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

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 · high confidence

Unauthenticated vulnerability in PeopleSoft Enterprise FIN Common Objects Brazil eProcurement component (version 9.1) allows remote attackers with HTTP network access to achieve complete system takeover due to high confidentiality, integrity, and availability impacts. The vulnerability is difficult to exploit (high attack complexity) but requires no authentication or user interaction.

MitigationRestrict network access to PeopleSoft eProcurement interfaces, implement WAF rules for known attack patterns, and apply Oracle's official patch when available. Consider disabling eProcurement if not business-critical until patched.

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 Common ObjectsApplication
Affected:= 9.1

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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 PeopleSoft FIN Common Objects installation
    Locate the PeopleSoft installation directory and check the version manifest or version.txt file for 'PeopleSoft Enterprise FIN Common Objects'. Common paths include $PS_HOME/fin/commonobjects or check the Oracle PeopleSoft PIA installation.
    Affected if The installed version of FIN Common Objects is exactly 9.1
  2. Verify Brazil eProcurement module is enabled
    Access the PeopleSoft Application Designer or check the module configuration files for the Brazil eProcurement component. Look for eProcurement-related service entries in the PeopleSoft configuration manager.
    Affected if The Brazil eProcurement (eProcurement Brazil) module is installed and enabled in the PeopleSoft environment
  3. Confirm eProcurement HTTP endpoints are exposed
    Check the web profile configuration or web server (WebLogic/IBM HTTP Server) bindings to determine if eProcurement servlets are mapped to accessible HTTP URLs. Review the psigw or piservlet mappings.
    Affected if eProcurement HTTP endpoints are accessible over the network without authentication barriers
  4. Check for unauthenticated access to eProcurement servlets
    Review the web.xml deployment descriptor and PeopleSoft permission lists for the eProcurement servlets. Verify if Anonymous user access is permitted to the eProcurement web components.
    Affected if Anonymous or unauthenticated access is permitted to eProcurement servlets in the web configuration

Your environment is affected if you have PeopleSoft Enterprise FIN Common Objects version 9.1 with the Brazil eProcurement module enabled and exposed via HTTP without authentication restrictions.

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

Restrict network access to PeopleSoft eProcurement interfaces, implement WAF rules for known attack patterns, and apply Oracle's official patch when available. Consider disabling eProcurement if not business-critical until patched.

Fix this in Peoplesoft Enterprise Fin Common Objects Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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