dbcve.org
Peoplesoft Enterprise Fin PayablesApplication · Oracle

CVE-2021-2044

MEDIUM · 6.5 CVSS v3.1 Published 2021-01-20
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 Payables product of Oracle PeopleSoft (component: Financial Sanctions). 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 Payables. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise FIN Payables 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 · high confidence

Vulnerability in the Financial Sanctions component of Oracle PeopleSoft Enterprise FIN Payables version 9.2. Allows low-privileged authenticated attackers with network access via HTTP to access critical or all accessible data within the FIN Payables module, resulting in high confidentiality impact.

MitigationApply Oracle's quarterly security patch for PeopleSoft Enterprise FIN Payables 9.2. Until patched, restrict network access to the PeopleSoft HTTP interfaces and ensure least-privilege access controls are enforced for user accounts.

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 PayablesApplication
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. Verify FIN Payables version
    Access PeopleSoft Application Designer or the PeopleSoft Enterprise Portal and navigate to About > Version Information for the FIN Payables module. Alternatively, query the PSVERSION and/or PSIMAGE tables for the FIN PayABLES application version.
    Affected if The installed version is exactly 9.2 (version 9.2.00)
  2. Confirm Financial Sanctions component is configured
    In PeopleSoft Fluid Navigator or Classic menu, locate the Financial Sanctions setup page under FIN Payables > Sanctions. Check if any sanctions configurations or rules are defined or active.
    Affected if Financial Sanctions component is present and accessible in the FIN Payables module
  3. Identify HTTP-accessible endpoints
    Review web profile configuration in PeopleSoft and confirm which HTTP listener URLs (/ps/...) are active. Check thePIA (PeopleSoft Internet Architecture) deployment configuration.
    Affected if HTTP/HTTPS network access to PeopleSoft application servers is enabled and exposed
  4. Review user account privileges
    Access PeopleSoft Security > User Profiles and examine the roles assigned to standard user accounts. Look for any low-privileged accounts with access to FIN Payables functionality.
    Affected if Low-privileged authenticated users exist with FIN Payables module access via HTTP
  5. Check network exposure of PeopleSoft interfaces
    Review firewall rules, load balancer configurations, and reverse proxy settings to determine if PeopleSoft HTTP ports (typically 80, 443, 8000-8001) are accessible from untrusted networks.
    Affected if PeopleSoft HTTP interfaces are reachable from outside the trusted network

You are affected if FIN Payables version is exactly 9.2, the Financial Sanctions component is accessible, and low-privileged users can access FIN Payables over HTTP from the network.

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 Oracle's quarterly security patch for PeopleSoft Enterprise FIN Payables 9.2. Until patched, restrict network access to the PeopleSoft HTTP interfaces and ensure least-privilege access controls are enforced for user accounts.

Fix this in Peoplesoft Enterprise Fin Payables Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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