CVE-2025-21545
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 PeopleTools product of Oracle PeopleSoft (component: OpenSearch). Supported versions that are affected are 8.60 and 8.61. 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 confidenceA denial of service vulnerability exists in the OpenSearch component of PeopleSoft Enterprise PeopleTools versions 8.60 and 8.61. An unauthenticated remote attacker can send specially crafted HTTP requests to cause the application to hang or crash repeatedly, resulting in complete availability loss.
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= 8.60= 8.61CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify PeopleTools versionLog into PeopleSoft Application Designer or check the PeopleTools version via the About page (Help > About). Alternatively, run the following SQL against the PSSTATUS table: SELECT TOOLS_REL FROM PSSTATUS;Affected if The installed version is exactly 8.60 or exactly 8.61.
-
Verify OpenSearch component is in useCheck if OpenSearch is installed and configured for PeopleSoft. Look for OpenSearch installation directories (typically under PS_HOME/opensearch or within the WebLogic domain). Confirm the OpenSearch service is running via Windows Services or Unix process list (ps -ef | grep opensearch).Affected if OpenSearch is installed and the OpenSearch service is running as part of the PeopleSoft environment.
-
Check OpenSearch port exposureIdentify the ports OpenSearch is listening on (default ports are 9200 and 9300). Run netstat -an | grep -E '9200|9300' or check firewall rules. Review network configuration to determine if these ports are accessible from external networks.Affected if OpenSearch ports (9200, 9300, or configured custom ports) are exposed to untrusted networks or the internet.
-
Review HTTP access logs for anomalous requestsExamine OpenSearch access logs (typically in the logs directory under the OpenSearch installation path) for unusual patterns, malformed requests, or high volumes of requests from single sources that could indicate DoS exploitation attempts.Affected if Logs show repeated malformed HTTP requests or unusual traffic patterns targeting OpenSearch endpoints.
A system is affected if it runs PeopleTools version 8.60 or 8.61 with the OpenSearch component installed and exposed to network access.
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's PeopleSoft Enterprise PeopleTools patches for versions 8.60 and 8.61 when available. If immediate patching is not possible, restrict network access to OpenSearch ports and implement rate limiting or Web Application Firewall rules to mitigate exploitation.
Upgrade to PeopleTools version 8.62 or later (once available with this fix) or apply the Oracle CPU patch for CVE-2025-21545
- 1. Subscribe to Oracle Critical Patch Updates and check My Oracle Support for the latest security patches for PeopleSoft Enterprise PeopleTools 8.60 and 8.61.
- 2. Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2025-21545 once released. Check Oracle's CPU advisory for the specific patch number and instructions.
- 3. Alternatively, monitor Oracle's PeopleSoft Enterprise PeopleTools release notes for a version that includes the security fix for this OpenSearch vulnerability.
- 4. After applying the patch or upgrading, verify the OpenSearch component is no longer vulnerable by testing the affected HTTP endpoints.
- 5. Test in a non-production environment before deploying to production to ensure stability.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21545 — 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-21545 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