dbcve.org
Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2025-53050

HIGH · 7.5 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to after 8.62 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 PeopleTools product of Oracle PeopleSoft (component: Performance Monitor). Supported versions that are affected are 8.60, 8.61 and 8.62. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of PeopleSoft Enterprise PeopleTools. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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

Denial of Service vulnerability in the Performance Monitor component of PeopleSoft Enterprise PeopleTools versions 8.60, 8.61, and 8.62. An unauthenticated remote attacker can send specially crafted HTTP requests to the Performance Monitor endpoint, causing the application to hang or experience a complete crash due to the High availability impact (CVSS:A:H).

MitigationApply Oracle Critical Patch Update for CVE-2025-53050. As an interim control, restrict network access to PeopleSoft HTTP listeners via firewall or WAF rules, and monitor for anomalous traffic patterns targeting the Performance Monitor 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
Peoplesoft Enterprise PeopletoolsApplication
Affected:>= 8.60, <= 8.62

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 installed PeopleTools version
    Locate the PeopleTools installation directory and check the version.properties or psver.txt file, or run the following SQL query against the database: SELECT VERSION FROM PSVERSION WHERE OBJECTTYPE = 'PPT';
    Affected if The version is 8.60, 8.61, or 8.62 (any version from 8.60 through 8.62 inclusive).
  2. Verify Performance Monitor component is enabled
    Check the PeopleSoft application configuration for Performance Monitor. This can be verified via the PeopleSoft Pure Internet Architecture administration pages under 'Performance Monitor' settings, or by querying the PSSTATUS table for PMN_ENABLED flag.
    Affected if Performance Monitor is enabled and configured in the environment.
  3. Confirm HTTP listener exposure for Performance Monitor
    Examine the web server configuration (weblogic.xml, web.xml, or IHS httpd.conf) to identify if the Performance Monitor HTTP endpoint is mapped and accessible. Common paths include /psp/*/servlet/perf or similar Performance Monitor servlets.
    Affected if The Performance Monitor HTTP endpoint is exposed through the web listeners without proper access restrictions.
  4. Audit network accessibility of PeopleSoft HTTP ports
    Review firewall rules, load balancer configurations, and web server access controls to determine if the PeopleSoft HTTP/HTTPS ports (typically 80, 443, 8000-9000) are accessible from untrusted networks. Use netstat or equivalent to list listening ports and verify binding addresses.
    Affected if PeopleSoft HTTP listeners are reachable from untrusted/external network segments.

You are affected if your environment runs PeopleTools 8.60-8.62, has Performance Monitor enabled, exposes the Performance Monitor HTTP endpoint, and allows unauthenticated network access to that endpoint.

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
Upgrade available Upgrade to a release after 8.62
Interim mitigation

Apply Oracle Critical Patch Update for CVE-2025-53050. As an interim control, restrict network access to PeopleSoft HTTP listeners via firewall or WAF rules, and monitor for anomalous traffic patterns targeting the Performance Monitor component.

Fix this in Peoplesoft Enterprise Peopletools Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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