CVE-2025-21537
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 Cash Management product of Oracle PeopleSoft (component: Cash 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 Cash Management. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise FIN Cash Management accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise FIN Cash Management accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 confidenceInjection vulnerability in PeopleSoft Enterprise FIN Cash Management component (version 9.2) allows low-privileged attackers with network access via HTTP to perform unauthorized read, insert, update, and delete operations on a subset of accessible data.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 Cash Management installationAccess PeopleSoft Application Designer or PeopleSoft Navigator and look for the Cash Management component under Financial Management > Cash Management. Alternatively, check the PS_CDM_TOP table in the database or consult your PeopleSoft installation inventory.Affected if The Cash Management component is present in the installation
-
Verify the PeopleSoft application versionLog into PeopleSoft Enterprise Portal as a system administrator and navigate to About > Version, or query the PSVERSION table for the release version. For FIN 9.2 specifically, check the Application Release level in PeopleSoft Configuration Manager or the PSSTATUS table.Affected if The installed version is exactly 9.2 (version equals 9.2, not higher or lower)
-
Confirm Cash Management component is enabledIn PeopleSoft Application Designer, verify the Cash Management component (e.g., CM_BANK, CM_BANK_BRANCH, CM_PAYMENT) exists and is not disabled. Also check permission lists (e.g., PTPT1000) and security roles to see if any roles have access to Cash Management web libraries.Affected if The Cash Management component is installed and accessible to any users through roles/permission lists
-
Check HTTP exposure of Cash ManagementReview web server configuration (web.xml,.properties files in PSIGW) or use a network scan to confirm the Cash Management service is exposed via HTTP/HTTPS ports (typically ports 80, 443, or custom PeopleSoft ports). Verify whether the component is accessible without VPN or proper network segmentation.Affected if The Cash Management component is network-accessible via HTTP without strict access controls
You are affected if your environment has PeopleSoft Enterprise FIN Cash Management installed at exactly version 9.2 and that component is accessible via HTTP to network users, regardless of whether you believe your permission controls are sufficient.
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.
dbcve · scopedApply Oracle Critical Patch Update for PeopleSoft Enterprise FIN 9.2 when available; restrict network access to trusted users and monitor for suspicious Cash Management activity.
Apply the Oracle Critical Patch Update that includes the fix for CVE-2025-21537
- Contact Oracle Support to obtain the specific Critical Patch Update (CPU) that addresses CVE-2025-21537 for PeopleSoft Enterprise FIN Cash Management 9.2
- Apply the Oracle CPU that includes the fix for this vulnerability
- After applying the patch, verify the Cash Management component is no longer vulnerable
- Restrict network access to PeopleSoft HTTP interfaces to only trusted users as an interim mitigation
- Review PeopleSoft user roles and permissions to ensure least-privilege access principles are followed
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-21537 — 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-2025-21537 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