CVE-2025-61758
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 IT Asset Management product of Oracle PeopleSoft (component: IT Asset 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 IT Asset Management. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise FIN IT Asset 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 confidenceOracle PeopleSoft Enterprise FIN IT Asset Management 9.2 contains a vulnerability in the IT Asset Management component that allows low-privileged authenticated attackers with network access via HTTP to gain unauthorized access to sensitive data. The CVSS vector indicates a network-based attack with low complexity, low privileges required, and high confidentiality impact.
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.
-
Verify PeopleSoft Enterprise FIN versionAccess PeopleSoft Internet Architecture (PIA) login page and check the version displayed, or query the PSVERSION table via SQL: SELECT VERSION FROM PSVERSION WHERE OBJECTTYPE='PORTAL'. Alternatively, check the PS_HOME directory for version files.Affected if The installed version is exactly 9.2 (version equals 9.2)
-
Confirm IT Asset Management component is provisionedLog into PeopleSoft and navigate to Enterprise Components > Integration Definitions > Component Interfaces, or query PSCLASSDEFN for ITAM-related component definitions. Check if the IT Asset Management (ITAM) module is present in the application.Affected if IT Asset Management component is installed and provisioned in the PeopleSoft environment
-
Verify HTTP network accessibilityConfirm the PIA HTTP listener is running and accessible externally. Check PeopleSoft domain configuration files (psappsrv.cfg, psigw.cfg) for web server bindings and network listeners.Affected if The PeopleSoft web tier is accessible over HTTP/HTTPS from network locations accessible to attackers
-
Check authentication configurationReview PeopleSoft authentication mechanisms in PIA configuration (psconfig.properties or via the Pure Internet Architecture). Determine if low-privileged users can authenticate through standard channels.Affected if Low-privileged user accounts exist and can authenticate to the PeopleSoft system via HTTP
-
Audit IT Asset Management data access permissionsQuery permission lists and roles assigned to standard users for ITAM-related menus (e.g., Asset Management > Asset Transactions). Check if unauthorized data exposure is possible through component interfaces.Affected if Low-privileged authenticated users have access to IT Asset Management data menus or component interfaces
The environment is affected if Oracle PeopleSoft Enterprise FIN version 9.2 is installed with the IT Asset Management component enabled and accessible via HTTP to low-privileged authenticated users.
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 the relevant Oracle Critical Patch Update for PeopleSoft Enterprise FIN IT Asset Management 9.2. If a patch is unavailable, implement compensating controls such as strict network segmentation, WAF rules to restrict unusual data access patterns, and enhanced monitoring of IT Asset Management endpoints.
- Contact Oracle Support and request the security patch for CVE-2025-61758
- Apply the Oracle Critical Patch Update that addresses this vulnerability
- After patching, verify the IT Asset Management component no longer allows unauthorized data access for low-privileged users
- Confirm the patch was applied successfully by reviewing Oracle's patch documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61758 — 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-61758 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