CVE-2025-21539
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 eSettlements product of Oracle PeopleSoft (component: eSettlements). 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 eSettlements. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise FIN eSettlements accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise FIN eSettlements 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 confidenceAccess control vulnerability in PeopleSoft Enterprise FIN eSettlements 9.2 allows low-privileged authenticated users via HTTP to perform unauthorized read, insert, update, or delete operations on a subset of accessible data. The vulnerability stems from missing or inadequate authorization checks in the eSettlements component.
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.
-
Confirm PeopleSoft FIN eSettlements versionQuery the PeopleSoft application version information for the eSettlements component. In PeopleSoft, this can typically be found via the About page (Help > About This Page) or by checking the PSVERSION table in the database for the eSettlements application version.Affected if The installed version matches exactly 9.2, as this is the only affected version per the CVE.
-
Verify eSettlements component is enabledCheck the PeopleSoft Application Designer or the web component registry to confirm the eSettlements module is deployed and accessible. Look for the eSettlements menu structure under the Financials menu.Affected if The eSettlements component is installed and accessible to users, which is required for the vulnerability to be exploitable.
-
Check user access to eSettlementsReview the PeopleSoft security configuration to identify which roles are granted access to eSettlements. Use the Permission Lists and Role pages in PeopleSoft Security to enumerate which low-privileged users have eSettlements access.Affected if Low-privileged or non-administrative users have any level of access to eSettlements, as the vulnerability allows unauthorized operations by authenticated users.
-
Inspect eSettlements authorization configurationReview the Row-Level Security and Component Security settings for eSettlements in PeopleSoft. Check whether proper authorization checks are configured for insert, update, and delete operations on sensitive data within eSettlements.Affected if Inadequate or missing authorization constraints are configured for eSettlements data access operations.
You are affected if PeopleSoft FIN eSettlements version 9.2 is installed with the eSettlements component enabled and low-privileged users can access it, as the vulnerability allows authenticated users to bypass authorization controls on a subset of data operations.
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 Update containing the fix for PeopleSoft FIN eSettlements 9.2. Restrict network access to eSettlements to authorized users only. Consider deploying a WAF as an interim control.
- 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-21539 — 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-21539 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